All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eial Czerwacki <eial@scalemp.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	"Shai Fultheim (Shai@ScaleMP.com)" <Shai@scalemp.com>
Subject: Re: [PATCH] AMD: modify cpu probe from APICID to initial APICID
Date: Wed, 26 Oct 2011 08:20:11 +0200	[thread overview]
Message-ID: <4EA7A69B.1050101@scalemp.com> (raw)
In-Reply-To: <CAE9FiQUrq-3GDhaZS8gOL5NBHF-ZcWjHiWWUYP4AdM2+q_12Ow@mail.gmail.com>

On 10/25/2011 11:51 PM, Yinghai Lu wrote:
> On Tue, Oct 25, 2011 at 4:49 AM, Eial Czerwacki<eial@scalemp.com>  wrote:
>> Make AMD probe processors using APICID rather than the initial APICID.
>>
>>
>> Signed-off-by: Eial Czerwacki<eial@scalemp.com>
>> Signed-off-by: Shai Fultheim<shai@scalemp.com>
>> ---
>>
>> --- a/arch/x86/kernel/cpu/amd.c 2011-09-14 05:58:19.542910736 -0700
>> +++ b/arch/x86/kernel/cpu/amd.c 2011-09-14 06:01:41.493209624 -0700
>> @@ -299,9 +299,9 @@ static void __cpuinit amd_detect_cmp(str
>>
>>         bits = c->x86_coreid_bits;
>>         /* Low order bits define the core id (index of core in socket) */
>> -       c->cpu_core_id = c->initial_apicid&      ((1<<      bits)-1);
>> +       c->cpu_core_id = c->apicid&      ((1<<      bits)-1);
>>         /* Convert the initial APIC ID into the socket ID */
>> -       c->phys_proc_id = c->initial_apicid>>      bits;
>> +       c->phys_proc_id = c->apicid>>      bits;
>>         /* use socket ID also for last level cache */
>>         per_cpu(cpu_llc_id, cpu) = c->phys_proc_id;
>>         /* fixup topology information on multi-node processors */
>>
>
> No, that is not right.
>
> We have to initial apicid to get socket/core mapping.
>
> BTW, your mail client has some problem with formatting.
>
> Thanks
>
> Yinghai
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

ok, I'll review the patch again.

is the format ok now?


Thanks,

Eial.

      reply	other threads:[~2011-10-26  6:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4EA6695C.1000904@scalemp.com>
     [not found] ` <9B14D1490DDECA4E974F6B9FC9EBAB3140CD274366@VMBX108.ihostexchange.net>
     [not found]   ` <4EA699B5.4030008@scalemp.com>
     [not found]     ` <9B14D1490DDECA4E974F6B9FC9EBAB3140CD27436C@VMBX108.ihostexchange.net>
2011-10-25 11:49       ` [PATCH] AMD: modify cpu probe from APICID to initial APICID Eial Czerwacki
2011-10-25 21:51         ` Yinghai Lu
2011-10-26  6:20           ` Eial Czerwacki [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=4EA7A69B.1050101@scalemp.com \
    --to=eial@scalemp.com \
    --cc=Shai@scalemp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yinghai@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.