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
> >> wrote:
> >>>
> Still setup_cpu_number() sucks.
> >>>
> >>> How about setup_cpu_and_node_numbe
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
>> wrote:
>>>
Still setup_cpu_number() sucks.
>>>
>>> How about setup_cpu_and_node_number()?
>>
>> setup_fast_cpu_node_nr()? setup_cpunr_regs()? I d
On Fri, 22 Jun 2018, Andy Lutomirski wrote:
> On Fri, Jun 22, 2018 at 11:02 AM Bae, Chang Seok
> 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
On Fri, Jun 22, 2018 at 11:02 AM Bae, Chang Seok
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?
> Still setup_cpu_number() sucks.
How about setup_cpu_and_node_number()?
Thanks,
Chang
On Fri, 22 Jun 2018, Andy Lutomirski wrote:
> > On Jun 22, 2018, at 8:18 AM, Thomas Gleixner wrote:
> >
> >> On Wed, 20 Jun 2018, Chang S. Bae wrote:
> >>
> >> +#ifdef CONFIG_X86_64
> >> +static void setup_cpu_number(int cpu)
> >
> > This function name is really misleading. vdso_setup_cpu_and_n
> On Jun 22, 2018, at 8:18 AM, Thomas Gleixner wrote:
>
>> On Wed, 20 Jun 2018, Chang S. Bae wrote:
>>
>> +#ifdef CONFIG_X86_64
>> +static void setup_cpu_number(int cpu)
>
> This function name is really misleading. vdso_setup_cpu_and_node() or
> something like that clearly tells what this is
On Wed, 20 Jun 2018, Chang S. Bae wrote:
>
> +#ifdef CONFIG_X86_64
> +static void setup_cpu_number(int cpu)
This function name is really misleading. vdso_setup_cpu_and_node() or
something like that clearly tells what this is about.
Thanks,
tglx
8 matches
Mail list logo