From: "Lu, Yinghai" <yinghai.lu@amd.com>
To: "Andi Kleen" <ak@muc.de>
Cc: "linux kernel mailing list" <linux-kernel@vger.kernel.org>,
yhlu.kernel@gmail.com
Subject: RE: [PATCH] x86_64: store Socket ID in phys_proc_id
Date: Tue, 17 Oct 2006 14:15:38 -0700 [thread overview]
Message-ID: <5986589C150B2F49A46483AC44C7BCA412D700@ssvlexmb2.amd.com> (raw)
From: Andi Kleen [mailto:ak@muc.de]
>> Socket ID is 0 for first Physical processor?
>It must just be some unique ID for each socket.
For dual core, if I lift AP's APIC ID and no touch BSP's APIC ID.
For example, BSP is still 0, and second core is 0x11.
The phys_proc_id will be 0 for BSP, and 8 for second core.
So I suggest you to use initial APIC ID to get socket id instead of APIC
ID.
YH
next reply other threads:[~2006-10-17 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 21:15 Lu, Yinghai [this message]
2006-10-18 13:04 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-10-18 17:15 Lu, Yinghai
2006-10-17 18:26 Lu, Yinghai
2006-10-17 20:58 ` Andi Kleen
2006-10-16 18:52 Lu, Yinghai
2006-10-17 15:34 ` Yinghai Lu
2006-10-17 17:53 ` Andi Kleen
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=5986589C150B2F49A46483AC44C7BCA412D700@ssvlexmb2.amd.com \
--to=yinghai.lu@amd.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.com \
/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
all inboxes | Powered by JetHome®