Re: Proposal for back-porting JFR to OpenJDK8u

guangyu.zhu guangyu.zhu at
Thu Jan 31 04:31:09 UTC 2019

The risk lies in other non-linux/x86-64 platforms. We have never built on them.

Sender:Hohensee, Paul <hohensee at>
Sent At:2019 Jan. 31 (Thu.) 08:45
Recipient:Andrew Hughes <gnu.andrew at>; Mario Torre <neugens at>
Cc:jdk8u-dev <jdk8u-dev-bounces at>; yumin qi <yumin.qi at>; jdk8u-dev <jdk8u-dev at>; kingsum.chow <kingsum.chow at>; denghui.ddh <denghui.ddh at>
Subject:Re: Proposal for back-porting JFR to OpenJDK8u

The backport is on the EnableJFR switch is true, but it's default false in the patch, so JFR is default off.


 On 1/30/19, 6:49 AM, "jdk8u-dev on behalf of Andrew Hughes" <jdk8u-dev-bounces at on behalf of gnu.andrew at> wrote:

    On Wed, 30 Jan 2019 at 09:15, Mario Torre <neugens at> wrote:
    > Yeah, however I think we may need to be conservative with this, since the
    > stability of the platform has precedence over new features, so we need to
    > find some way to have a staging environment for those changes.
    > Cheers,
    > Mario
    > On Wed, Jan 30, 2019 at 9:37 AM guangyu.zhu <guangyu.zhu at> wrote:
    > > Good suggestion! Paul
    > >
    > > Thanks,
    > > Guangyu
    > >

    I like Paul's suggestion. It's easier to have the core work in there
    and easily available
    for everyone to work on, than to try and create one perfect patch.
    It's also then easier
    to track what follow-on bugs have been fixed in 8u.

    Does the initial patch allow this to be disabled? The risk is
    significantly reduced if it
    is still possible to build as now with it applied.

    Andrew :)

    Senior Free Java Software Engineer
    Red Hat, Inc. (

    Web Site:
    PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://
    Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222

More information about the jdk8u-dev mailing list