From: "Bin.Cheng" <amker.cheng@gmail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Li Bin <huawei.libin@huawei.com>,
duwe@suse.de, Szabolcs Nagy <szabolcs.nagy@arm.com>,
Richard Earnshaw <rearnsha@arm.com>,
"takahiro.akashi@linaro.org" <takahiro.akashi@linaro.org>
Subject: Re: Any future plan supporting livepatching in kernel for AArch64?
Date: Thu, 19 Sep 2019 05:17:00 -0000 [thread overview]
Message-ID: <CAHFci29cinH_LibrnuueK=iL_1japoChw=uRHf+_NFhScL3EPA@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1m4e+vr-XgTHRUXoys2b4Cr3TmLy-qU_P-LUd9q_h28OQ@mail.gmail.com>
On Thu, Sep 19, 2019 at 1:02 PM Andrew Pinski <pinskia@gmail.com> wrote:
>
> On Wed, Sep 18, 2019 at 9:56 PM Andrew Pinski <pinskia@gmail.com> wrote:
> >
> > On Wed, Sep 18, 2019 at 9:24 PM Bin.Cheng <amker.cheng@gmail.com> wrote:
> > >
> > > Hi,
> > > I read through previous messages which tried to support livepatching
> > > in kernel for AArch64.
> > > Following is the patch supporting mfentry:
> > > https://gcc.gnu.org/ml/gcc-patches/2016-03/msg00756.html
> > > And this is the last message about above thread:
> > > https://gcc.gnu.org/ml/gcc-patches/2016-04/msg01093.html
> > >
> > > Here is another patch trying to support a general option, however. it
> > > was not merged either.
> > > https://gcc.gnu.org/ml/gcc-patches/2016-12/msg01791.html
> > >
> > > If I read messages correctly, kernel part is not merged (partly)
> > > because of waiting for GCC. As a result, we have to apply local
> > > patches, I am wondering if there is any future plan to support it on
> > > AArch64, or no one really uses it?
> >
> > A GCC patch was merged for this already and is included in GCC 9.1.0 and above.
> > See https://gcc.gnu.org/onlinedocs/gcc-9.2.0/gcc/Common-Function-Attributes.html#index-patchable_005ffunction_005fentry-function-attribute
> > And
> > https://gcc.gnu.org/onlinedocs/gcc-9.2.0/gcc/Instrumentation-Options.html#index-fpatchable-function-entry
> >
> > Someone did not add it to the GCC 9 release notes though to highlight it.
> Note I Mean GCC 8 release notes as it was included in GCC 8.1.0 and above :).
>
> Also see https://lkml.org/lkml/2017/10/13/340 for the Linux side of
> discussion about this option :).
Thank you very much, the option name changed several times and I
missed this one!
Thanks,
bin
>
>
> >
> > Thanks,
> > Andrew Pinski
> >
> > >
> > > I CCed patch authors as well as who joined previous discussions,
> > > please let me know if you don't want to be cced in this thread.
> > >
> > > Thanks,
> > > bin
prev parent reply other threads:[~2019-09-19 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 4:23 Bin.Cheng
2019-09-19 4:56 ` Andrew Pinski
2019-09-19 5:02 ` Andrew Pinski
2019-09-19 5:17 ` Bin.Cheng [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHFci29cinH_LibrnuueK=iL_1japoChw=uRHf+_NFhScL3EPA@mail.gmail.com' \
--to=amker.cheng@gmail.com \
--cc=duwe@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=huawei.libin@huawei.com \
--cc=maxim.kuvyrkov@linaro.org \
--cc=pinskia@gmail.com \
--cc=rearnsha@arm.com \
--cc=szabolcs.nagy@arm.com \
--cc=takahiro.akashi@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).