From: "H. Peter Anvin" <hpa@zytor.com>
To: ananth@in.ibm.com
Cc: Yinghai Lu <yinghai@kernel.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 3/4] x86: using logical flat for amd cpu too.
Date: Tue, 12 Jan 2010 14:50:58 -0800 [thread overview]
Message-ID: <4B4CFCD2.6000000@zytor.com> (raw)
In-Reply-To: <20100112082706.GE28425@in.ibm.com>
On 01/12/2010 12:27 AM, Ananth N Mavinakayanahalli wrote:
> On Mon, Jan 11, 2010 at 06:48:01PM -0800, Yinghai Lu wrote:
>
>> not sure it works again, could be bios fix the irq routing dest ?
>
> Nope, it doesn't. I applied this patchset.. no luck.
Okay, I have been monitoring this discussion, but I would like to make
sure I have understood all the relevant details:
1. The original patch is already reverted in Linus' tree.
2. The Intel/AMD thing is likely to be a red herring; specifically it's
a proxy for some other platform difference.
3. There is at least one platform ("an IBM platform with two quad-core
Xeon X7350 CPUs" -- which platform?) for which the logical
destination mode fails even though it should have been supported.
Currently there is no known workaround for this platform other than
forcing physical mode on this machine, which is what the current
code does, for valid or invalid reasons.
It would be good to clean up this code for .34, and I would really like
to know *which* platform this is; furthermore, Ananth, if you could send
as much technical information on this platform as possible including DMI
and lspci dumps I would appreciate it.
Furthermore, is this a production or preproduction system?
-hpa
next prev parent reply other threads:[~2010-01-12 22:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 2:48 [RFC PATCH 1/4] use nr_cpus= to set nr_cpu_ids early Yinghai Lu
2010-01-12 2:48 ` [RFC PATCH 3/4] x86: using logical flat for amd cpu too Yinghai Lu
2010-01-12 3:16 ` Linus Torvalds
2010-01-12 8:47 ` Yinghai Lu
2010-01-12 8:27 ` Ananth N Mavinakayanahalli
2010-01-12 22:50 ` H. Peter Anvin [this message]
2010-01-13 4:53 ` Ananth N Mavinakayanahalli
2010-01-12 2:48 ` [RFC PATCH 4/4] x86: according to nr_cpu_ids to decide if need to leave logical flat Yinghai Lu
2010-01-12 3:20 ` Linus Torvalds
2010-01-12 8:50 ` Yinghai Lu
2010-01-12 2:48 ` [RFC PATCH 2/4] x86: use dmi check to treat disabled cpus as hotplug cpus Yinghai Lu
2010-01-12 3:13 ` Linus Torvalds
2010-01-12 8:59 ` Yinghai Lu
2010-01-12 15:19 ` Linus Torvalds
2010-01-12 17:54 ` Suresh Siddha
2010-01-12 18:13 ` Yinghai Lu
2010-01-12 18:24 ` Suresh Siddha
2010-01-12 19:19 ` Yinghai Lu
2010-01-12 9:15 ` Yinghai Lu
2010-01-12 9:46 ` Ingo Molnar
2010-01-12 16:14 ` Valdis.Kletnieks
2010-01-12 16:26 ` Linus Torvalds
2010-01-12 17:17 ` Valdis.Kletnieks
2010-01-12 3:06 ` [RFC PATCH 1/4] use nr_cpus= to set nr_cpu_ids early Linus Torvalds
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=4B4CFCD2.6000000@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox