From: Sumit Garg <sumit.garg@linaro.org>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Oliver Sang <oliver.sang@intel.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
jbaron@akamai.com, lkp@lists.01.org,
kbuild test robot <lkp@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] objtool,static_call: Don't emit static_call_site for .exit.text
Date: Thu, 18 Mar 2021 10:12:43 +0530 [thread overview]
Message-ID: <CAFA6WYOM=y_8x=ziehOMKMFh1Va0_W6nmXfYtxKE28fM0BumPQ@mail.gmail.com> (raw)
In-Reply-To: <YFJ66nW0vabAgGqm@kernel.org>
On Thu, 18 Mar 2021 at 03:26, Jarkko Sakkinen <jarkko@kernel.org> wrote:
>
> On Wed, Mar 17, 2021 at 07:07:07PM +0530, Sumit Garg wrote:
> > On Wed, 17 Mar 2021 at 18:16, Peter Zijlstra <peterz@infradead.org> wrote:
> > >
> > > On Wed, Mar 17, 2021 at 05:25:48PM +0530, Sumit Garg wrote:
> > > > Thanks Peter for this fix. It does work for me on qemu for x86. Can
> > > > you turn this into a proper fix patch? BTW, feel free to add:
> > >
> > > Per the below, the original patch ought to be fixed as well, to not use
> > > static_call() in __exit.
> >
> > Okay, fair enough.
> >
> > Jarkko,
> >
> > Can you please incorporate the following change to the original patch as well?
>
> Can you roll-out a proper patch of this?
Okay, I will post a separate patch for this.
-Sumit
>
> /Jarkko
next prev parent reply other threads:[~2021-03-18 4:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210315142345.GB4401@xsang-OptiPlex-9020>
[not found] ` <CAFA6WYNMHAqqmNfncmJm3+BUYCktXouRtV_udSxQb7eifPmX+Q@mail.gmail.com>
[not found] ` <20210317030101.GB22345@xsang-OptiPlex-9020>
[not found] ` <CAFA6WYMb-C2L7DmGnhWgxjuuvP=qxPA4-s4q+knxH+iWXypHmw@mail.gmail.com>
[not found] ` <YFHAsgNhe8c3ZHQN@hirez.programming.kicks-ass.net>
[not found] ` <YFHE9CjanDAD4l5M@hirez.programming.kicks-ass.net>
[not found] ` <YFHFjarVo7HAP7pg@hirez.programming.kicks-ass.net>
[not found] ` <CAFA6WYNs-rQLUGPMwc-p0q_KRvR16rm-x55gDqw828c7-C1qeA@mail.gmail.com>
2021-03-17 12:45 ` [PATCH] objtool,static_call: Don't emit static_call_site for .exit.text Peter Zijlstra
2021-03-17 13:37 ` Sumit Garg
2021-03-17 21:55 ` Jarkko Sakkinen
2021-03-18 4:42 ` Sumit Garg [this message]
2021-03-17 21:01 ` Jarkko Sakkinen
2021-03-18 0:02 ` Josh Poimboeuf
2021-03-18 7:59 ` Peter Zijlstra
2021-03-18 8:30 ` Peter Zijlstra
2021-03-18 8:47 ` Peter Zijlstra
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='CAFA6WYOM=y_8x=ziehOMKMFh1Va0_W6nmXfYtxKE28fM0BumPQ@mail.gmail.com' \
--to=sumit.garg@linaro.org \
--cc=jarkko@kernel.org \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.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 NNTP newsgroup(s).