From: Ingo Molnar <mingo@elte.hu>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
hpa@zytor.com, tglx@linutronix.de,
Yinghai Lu <yhlu.kernel@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Intel x86_64 llc_shared_map/cpu_llc_id anomolies
Date: Fri, 19 Dec 2008 09:15:17 +0100 [thread overview]
Message-ID: <20081219081517.GA7859@elte.hu> (raw)
In-Reply-To: <20081219020921.GD26490@linux-os.sc.intel.com>
* Suresh Siddha <suresh.b.siddha@intel.com> wrote:
> > Is cpu_llc_id supposed to be unique across blades? I assume
> > llc_shared_map should not be showing shared cache across blades.
>
> x86 folks, Appended patch fixes the reported issue. Please apply.
applied, thanks Suresh!
Not for v2.6.28 because that is going to be released in a few days and
these sorts of changes can easily cause boot regressions - but i marked it
for -stable backport so it will hit .28.1 if everything is fine.
Ingo
prev parent reply other threads:[~2008-12-19 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 21:42 Intel x86_64 llc_shared_map/cpu_llc_id anomolies Dimitri Sivanich
2008-12-12 21:59 ` Yinghai Lu
2008-12-19 2:09 ` Suresh Siddha
2008-12-19 8:15 ` Ingo Molnar [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=20081219081517.GA7859@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sivanich@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox