-
Notifications
You must be signed in to change notification settings - Fork 124
8366093: [lworld] Add preview mode to C++ classloader #1618
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
base: lworld
Are you sure you want to change the base?
Conversation
This is a new version of #1609, re-created so there's now a pr/xxx branch for use by dependent PRs. |
👋 Welcome back david-beaumont! A progress list of the required criteria for merging this PR into |
@david-beaumont This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 654 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. ➡️ To flag this PR as ready for integration with the above commit message, type |
enum { | ||
// Set on a "normal" (non-preview) location if a preview version of | ||
// it exists in the same module. | ||
FLAGS_HAS_PREVIEW_VERSION = 0x1, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid confusion, the value and spelling of the flag should agree across all modules.
In ImageLocation and jimage/ModulesReference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ModulesReference are different flags, with different semantics. That's why I made sure they were private and provided helper methods for reading/writing the package directory offsets (because I did trip over using the wrong constants at one point).
I agree it's weird/annoying to have this similar-but-different set of flags, but the ModuleReference flags are completely encapsulated in one place, so cannot be accidentally confused with, or misused in place of the ImageLocation flags.
These flags have a requirement of being zero for almost all entries to reduce image file size, while the ModulesReference flags need to additive for merging (and are not stored in the same part of the jimage file).
I could change flag ordering to make the values of the "has preview version" flags match, but since these sets of flags must never be mistaken for each other, I'm not sure that's beneficial (if anything it might foster the idea that they can be used interchangeably in some way).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If they have the same spelling, they will cause confusion if they have different semantics and usages.
All of imageFile, jimage, and the file system provider and classloader are in a single scope of operation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've done this now (but I don't really agree with the argument that it will be likely to cause confusion however, since the flags are stored in different data structures and their use is carefully encapsulated).
// Flag masks for the ATTRIBUTE_PREVIEW_FLAGS attribute. Defined so | ||
// that zero is the overwhelmingly common case for normal resources. | ||
enum { | ||
// Set on a "normal" (non-preview) location if a preview version of | ||
// it exists in the same module. | ||
FLAGS_HAS_PREVIEW_VERSION = 0x1, | ||
// Set on all preview locations in "/modules/xxx/META-INF/preview/..." | ||
FLAGS_IS_PREVIEW_VERSION = 0x2, | ||
// Set on a preview location if no normal (non-preview) version of | ||
// it exists in the same module. | ||
FLAGS_IS_PREVIEW_ONLY = 0x4 | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A refactoring of the flags can avoid conflicting states.
FLAGS_IS_PREVIEW_VERSION = 2; // set for preview version
FLAGS_NO_NORMAL_VERSION = 1; // preserving the zero value for normal and no preview.
Create static methods in ImageLocation to perform the desired tests on flags.
The utility methods make the code easier to read.
Also define macros/function in the native code in ImageFile and jimage.
isPreviewVersion(flags) { return (flags & FLAGS_IS_PREVIEW_VERSION) != 0)}
isPreviewOnly(flags) { return (flags & FLAGS_IS_REVIEW_VERSION | FLAGS_NO_NORMAL_VERSION) == FLAGS_NO_NORMAL_VERSION}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reprise:
Your name FLAGS_IS_PREVIEW_ONLY probably better than FLAGS_NO_NORMAL_VERSION and has the same semantics.
FLAGS_HAS_PREVIEW_VERSION means that there is a preview version and it will be found in the <META-INF/Preview> hierarchy. if the flag is in the preview node then this is it. If found in the normal hierarchy, the preview class is found in the <META-INF/Preview> hierarchy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The FLAGS_HAS_PREVIEW_VERSION flag is only set on non-preview locations. It's what indicates that you may need to look for a preview version in preview mode (rare but possible).
For C++ I think this occasional 2nd hash calculation and lookup shouldn't be an issue because it's for class loading, so each successful lookup triggers a lot of additional work (and as I understand it, failed lookups for the preview-only cases should not be common in this code -- as opposed to the JRT file system code).
There are several possible approaches to address this if it does turn out to be a performance issue though (e.g. making preview string hashes a simple modification of non-preview string hashes).
size_t name_len = strlen(name); | ||
size_t preview_infix_len = strlen(preview_infix); | ||
|
||
// TBD: assert(module_name_len > 0 && "module name must be non-empty"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TBD: is obsolete?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't use multiple white-space, so this wasn't me. It's just line 113 in the old code moved.
I don't know enough to change it confidently.
// Regardless of preview mode, don't return resources requested directly | ||
// via their preview path. | ||
if ((flags & ImageLocation::FLAGS_IS_PREVIEW_VERSION) != 0) { | ||
return 0L; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can this occur?
classloader is the only client and does not pass arbitrary paths.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hopefully it can't, but I'm not taking chances.
u4 flags = loc.get_preview_flags(); | ||
// No preview flags means "a normal resource, without a preview version". | ||
// This is the overwhelmingly common case, with or without preview mode. | ||
if (flags == 0) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should test for defined flags, ignoring bits outside of the defined bits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this really needs to be zero in this case, because otherwise it will be adding a lot of space to the jimage file for all the attributes that need to be encoded (see comment on line 248 in imageFile.hpp).
enum { | ||
// Set on a "normal" (non-preview) location if a preview version of | ||
// it exists in the same module. | ||
FLAGS_HAS_PREVIEW_VERSION = 0x1, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If they have the same spelling, they will cause confusion if they have different semantics and usages.
All of imageFile, jimage, and the file system provider and classloader are in a single scope of operation.
#define DISABLE_PREVIEW_PATCHING_DEFAULT false | ||
|
||
bool Arguments::disable_preview_patching() { | ||
const char* prop = get_property("DISABLE_PREVIEW_PATCHING"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick, feel free to ignore, esp. since this is temporary. I think it would make the code easier to follow if this was enable preview patching, defaulting to true. It stands in contrast toEnableValhalla
and enable_preview()
. But as said, not a huge thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The naming was Roger's, I'm mostly happy with anything really if it's temporary.
I have a similar preference for positive naming ("enable" rather than "disable") to avoid double negatives, but in this case it's probably more work to do that (since it'll cause a rebase of 3 other PRs in progress) than just live with it for a few weeks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Disclaimer: I can only speak for the runtime portions of the code.
|
||
// Closes and clears the JImage file reference (this will only be called during shutdown). | ||
static void jimage_close() { | ||
if (JImage_file != nullptr) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not familiar with jimage at all, is there as reason we could close a non-open jimage? And following from that, can we guarantee to not call jimage_open on an open jimage? (Maybe an assert should guard it?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I honestly don't know, so this is the old behaviour, so I'm keeping it for now.
Alan might know more.
// Looks up the location of a named JImage resource. This "raw" lookup function allows | ||
// the preview mode to be manually specified, so must not be accessible outside this | ||
// class. ClassPathImageEntry manages all calls for resources after startup is complete. | ||
static JImageLocationRef jimage_find_resource(const char* module_name, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function makes the rest of the code more legible. Thanks!
// be read so this code can be committed before image writing changes | ||
// for preview mode. Preview mode changes do not modify any structure, | ||
// so a 1.0 file will look like a jimage without any preview resources. | ||
// TODO: Restore equality check for MINOR_VERSION. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this something you still have to address in this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need to address it later, when the image writing code is changed.
C++ changes for supporting preview mode when preview mode resources (with new location flags) are available.
At the moment, this code will operate on non-preview jimage files (1.0) and act as if no preview resources are available by virtue of the default value for missing attributes being zero (which matches location flags for "normal" entries).
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/valhalla.git pull/1618/head:pull/1618
$ git checkout pull/1618
Update a local copy of the PR:
$ git checkout pull/1618
$ git pull https://git.openjdk.org/valhalla.git pull/1618/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1618
View PR using the GUI difftool:
$ git pr show -t 1618
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/valhalla/pull/1618.diff
Using Webrev
Link to Webrev Comment