Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix Runtime Instrumentation Control Block Mapping #2497

Merged
merged 2 commits into from
Jul 27, 2018

Conversation

dhong44
Copy link
Contributor

@dhong44 dhong44 commented Jul 27, 2018

Remove mapping to suspension control at word 6 byte 3 bit 4
which should be reserved and add mappings for suppression
control and guarded storage.

Signed-off-by: Daniel Hong [email protected]

Remove mapping to suspension control at word 6 byte 3 bit 4
which should be reserved and add mappings for suppression
control and guarded storage.

Signed-off-by: Daniel Hong <[email protected]>
@dhong44
Copy link
Contributor Author

dhong44 commented Jul 27, 2018

@fjeremic

uint32_t pad3:2;

uint32_t guardedStorage:1;
uint32_t pad3:1;
Copy link
Contributor

@fjeremic fjeremic Jul 27, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we use a better name for the paddings? It would be much easier to make sure the offsets are correct if for example pad3 was renamed to be something like padAtBit15. Similarly elsewhere.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, with the first padding, pad29, is that name clear since it is a 29 bit padding at the start of word 6 or should we think of something more descriptive?

Copy link
Contributor

@fjeremic fjeremic Jul 27, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make the naming consistent. I'm not picky about what it should be. It shouldn't matter whether the pad is at the start on in the middle. The name should be descriptive enough to tell you where the padding is. The bit field will always tell how big the padding is.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fjeremic fjeremic self-assigned this Jul 27, 2018
Change padding names inj9ri.h to indicate the start of
padding with both the word and bit number.

Signed-off-by: Daniel Hong <[email protected]>
@fjeremic
Copy link
Contributor

Jenkins test sanity depends eclipse/omr#master

@dhong44
Copy link
Contributor Author

dhong44 commented Jul 27, 2018

Looks like failures are due to #2129

@fjeremic
Copy link
Contributor

Travis builds will fail until we have an OMR promotion. We should be good here.

@fjeremic fjeremic merged commit 490e91f into eclipse-openj9:master Jul 27, 2018
@dhong44 dhong44 deleted the fixRIMapping branch July 30, 2018 13:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants