From: Borislav Petkov <bp@alien8.de>
To: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Daniel J Blueman <daniel@numascale-asia.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] NumaScale changes
Date: Thu, 10 Jan 2013 16:28:13 +0100 [thread overview]
Message-ID: <20130110152813.GG23008@liondog.tnic> (raw)
Hi guys,
those changes have been a bit longer in the works and were ready even
before the merge window but it was better to hold them off after it and
send them out then. They basically incorporate PCI domain numbers into
AMD northbridge IDs, thus adding support for Numascale confederated
systems.
Please pull,
thanks.
--
The following changes since commit 9931faca02c604c22335f5a935a501bb2ace6e20:
Linux 3.8-rc3 (2013-01-09 18:59:55 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git tags/numascale
for you to fetch changes up to c7e5301a1b7c3f47af635a8b1b14480b81426025:
amd64_edac: Fix type usage in NB IDs and memory ranges (2013-01-10 16:18:00 +0100)
----------------------------------------------------------------
This patchset adds support for federated systems where multiple memory
controllers can exist and see each other over multiple PCI domains. This
basically means that AMD node ids can be more than 8 now and the code
handling this is taught to incorporate PCI domain into those IDs.
----------------------------------------------------------------
Daniel J Blueman (4):
x86, AMD, NB: Add multi-domain support
x86, AMD, NB: Use u16 for northbridge IDs in amd_get_nb_id
amd64_edac: Fix PCI function lookup
amd64_edac: Fix type usage in NB IDs and memory ranges
arch/x86/include/asm/amd_nb.h | 17 ++++++++++++++++
arch/x86/include/asm/processor.h | 2 +-
arch/x86/kernel/cpu/amd.c | 4 ++--
drivers/edac/amd64_edac.c | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------------
drivers/edac/amd64_edac.h | 12 +++--------
5 files changed, 80 insertions(+), 64 deletions(-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
reply other threads:[~2013-01-10 15:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130110152813.GG23008@liondog.tnic \
--to=bp@alien8.de \
--cc=daniel@numascale-asia.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).