[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180119003443.a58188a04552897d7fb78dbc@kernel.org>
Date: Fri, 19 Jan 2018 00:34:43 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: "Woodhouse, David" <dwmw@...zon.co.uk>
Cc: mhiramat@...nel.org, "mingo@...nel.org" <mingo@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
"hpa@...or.com" <hpa@...or.com>,
"ananth@...ux.vnet.ibm.com" <ananth@...ux.vnet.ibm.com>,
"gregkh@...ux-foundation.org" <gregkh@...ux-foundation.org>
Subject: Re: [PATCH v1 tip/master 1/3] retpoline: Introduce start/end
markers of indirect thunk
On Thu, 18 Jan 2018 12:06:10 +0000
"Woodhouse, David" <dwmw@...zon.co.uk> wrote:
> On Thu, 2018-01-18 at 21:01 +0900, Masami Hiramatsu wrote:
> >
> > +#define X86_INDIRECT_THUNK(reg) \
> > + *(.text.__x86.indirect_thunk.##reg)
>
> Note that we don't actually care about those being in their own
> section, named after the register. That was just a hangover from the
> initial GCC COMDAT implementation.
>
> If it makes your life easier just to put them all in a single section,
> go ahead.
Got it. I just concerned that gcc was using this section.
I'll make it ".text.__x86.indirect_thunk" to consolidate.
Thanks!
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists