From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel J Blueman <daniel@numascale-asia.com>
Cc: Borislav Petkov <bp@amd64.org>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Steffen Persvold <sp@numascale.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RFC: Fix AMD Northbridge-ID contiguity assumptions
Date: Wed, 03 Oct 2012 08:16:02 -0700 [thread overview]
Message-ID: <506C56B2.50505@zytor.com> (raw)
In-Reply-To: <1349256029-14851-1-git-send-email-daniel@numascale-asia.com>
On 10/03/2012 02:20 AM, Daniel J Blueman wrote:
> The AMD Northbridge initialisation code and EDAC assume the Northbridge IDs
> are contiguous, which no longer holds on federated systems with multiple
> HyperTransport fabrics with multiple PCI domains.
Is that "on NumaScale systems"? If so, please say so rather than trying
to make it sound generic; if it is not, can you give some other examples?
-hpa
next prev parent reply other threads:[~2012-10-03 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 9:20 [PATCH] RFC: Fix AMD Northbridge-ID contiguity assumptions Daniel J Blueman
2012-10-03 15:16 ` H. Peter Anvin [this message]
[not found] ` <CAP-4_fVhkjb=0YdYz37PEg3Or-hbRO8F40tHqEsRCC-pYY_HOg@mail.gmail.com>
2012-10-03 15:50 ` H. Peter Anvin
2012-10-03 18:08 ` Borislav Petkov
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=506C56B2.50505@zytor.com \
--to=hpa@zytor.com \
--cc=bp@amd64.org \
--cc=daniel@numascale-asia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sp@numascale.com \
--cc=tglx@linutronix.de \
--cc=x86@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.