RFR: 8223147: JFR Backport (to jdk8u)
andrey at azul.com
Mon Aug 12 11:36:51 UTC 2019
My understanding is that these changes are to compliment the work/fix the bugs I've done under 8223147 (main backport issue).
These do not have openjdk bug numbers because correspond to changes made by Oracle privately, before JFR was open-sourced.
In other words - the functionality they bring is already part of openjdk jdk11, however expressed in some different code (since otherwise I
would just brought it under 8223147). So it required jdk8-specific way to make it happen in jdk8, which was generously done by Alibaba team
Hope this clarifies
> On 12 Aug 2019, at 11:50, Mario Torre <neugens at redhat.com> wrote:
> Hi Denghui,
> I'm a bit confused because none of those seems to be a backport bug.
> For example, the 8223689 isn't in 11. As such, we should first port
> changes to the topmost upstream release and than carry them down one
> by one until it reaches 8, in other words we should request the
> changes to go first in 14, then 13, then 11 then 8.
> We can of course apply single fixes in 8 that do not qualify for the
> other releases, for example (I have yet to try) if 8229401 is only
> valid because of the backport to 8 then it's fine to only fix this
> problem in 8, otherwise we need to go the full route.
> On Mon, Aug 12, 2019 at 10:32 AM DDH <denghui.ddh at alibaba-inc.com> wrote:
>> Hi Mario、Andrey,
>> We(Alibaba) recently fixed some test failures about JFR CodeCache events, which are incremental changes based on Azul' patchset.
>> 8229401: Fix JFR code cache test failures
>> The other patchset we provided earlier is as follows:
>> 8223689: Add JFR Thread Sampling Support
>> 8223690: Add JFR BiasedLock Event Support
>> 8223691: Add JFR G1 Region Type Change Event Support
>> 8223692: Add JFR G1 Heap Summary Event Support
> Mario Torre
> Associate Manager, Software Engineering
> Red Hat GmbH <https://www.redhat.com>
> 9704 A60C B4BE A8B8 0F30 9205 5D7E 4952 3F65 7898
More information about the jdk8u-dev