From: Ingo Molnar <mingo@elte.hu>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: hpa@zytor.com, tglx@linutronix.de, linux-kernel@vger.kernel.org,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [patch 2/2] x2apic: use x2apic id reported by cpuid during topology discovery
Date: Tue, 19 Aug 2008 02:24:02 +0200 [thread overview]
Message-ID: <20080819002402.GG9914@elte.hu> (raw)
In-Reply-To: <20080818181435.670402000@linux-os.sc.intel.com>
* Suresh Siddha <suresh.b.siddha@intel.com> wrote:
> use x2apic id reported by cpuid during topology discovery, instead of the
> apic id configured in the APIC. For most of the systems, x2apic id
> reported by cpuid leaf 0xb will be same as the physical apic id reported
> by the APIC_ID register of the APIC. We follow the suggested guidelines
> and use the apic id reported by the cpuid.
>
> No change to non-generic UV platforms, will use the apic id reported in the
> APIC_ID register as the cpuid reported apic id's may not be unique.
>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
applied both fixes to tip/x86/x2apic - thanks Suresh!
Ingo
next prev parent reply other threads:[~2008-08-19 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 18:13 [patch 1/2] x2apic: use cpuid vector 0xb when available for detecting cpu topology Suresh Siddha
2008-08-18 18:13 ` [patch 2/2] x2apic: use x2apic id reported by cpuid during topology discovery Suresh Siddha
2008-08-19 0:24 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-26 18:38 [patch 1/2] x2apic: use cpuid vector 0xb when available for detecting cpu topology - v2 Suresh Siddha
2008-08-26 18:38 ` [patch 2/2] x2apic: use x2apic id reported by cpuid during topology discovery Suresh Siddha
2008-08-27 7:04 ` Ingo Molnar
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=20080819002402.GG9914@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--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 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.