[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1806252140260.1587@nanos.tec.linutronix.de>
Date: Mon, 25 Jun 2018 21:40:40 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "H. Peter Anvin" <hpa@...or.com>
cc: Andy Lutomirski <luto@...nel.org>,
"Bae, Chang Seok" <chang.seok.bae@...el.com>,
Ingo Molnar <mingo@...nel.org>,
Andi Kleen <ak@...ux.intel.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"Metzger, Markus T" <markus.t.metzger@...el.com>,
"Ravi V. Shankar" <ravi.v.shankar@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v4 7/7] x86/vdso: Move out the CPU number store
On Mon, 25 Jun 2018, H. Peter Anvin wrote:
> On 06/25/18 08:40, Thomas Gleixner wrote:
> > On Fri, 22 Jun 2018, Andy Lutomirski wrote:
> >
> >> On Fri, Jun 22, 2018 at 11:02 AM Bae, Chang Seok
> >> <chang.seok.bae@...el.com> wrote:
> >>>
> >>>> Still setup_cpu_number() sucks.
> >>>
> >>> How about setup_cpu_and_node_number()?
> >>
> >> setup_fast_cpu_node_nr()? setup_cpunr_regs()? I don't have any
> >> brilliant ideas. Thomas?
> >
> > It's really hard to find a good one. setup_cpu_node_cache() might work, but
> > it's not brilliant either.
> >
>
> Since this applies to the getcpu(2) system call (in addition to the
> kernel usage), perhaps setup_getcpu()?
Works for me.
Powered by blists - more mailing lists