linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Herrmann <andreas.herrmann3@amd.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	<linux-pci@vger.kernel.org>
Subject: Re: [andreas.herrmann3@amd.com: [PATCH 1/2] x86/amd: Restore early_fill_mp_bus_to_node]
Date: Tue, 28 Feb 2012 18:42:32 +0100	[thread overview]
Message-ID: <20120228174232.GI31006@alberich.amd.com> (raw)
In-Reply-To: <20120227122240.778bcc5b@jbarnes-desktop>

On Mon, Feb 27, 2012 at 12:22:40PM -0800, Jesse Barnes wrote:
> On Mon, 27 Feb 2012 10:44:06 +0100
> Ingo Molnar <mingo@elte.hu> wrote:
> 
> > 
> > Yours?
> > 
> > ----- Forwarded message from Andreas Herrmann <andreas.herrmann3@amd.com> -----
> > 
> > Date: Fri, 24 Feb 2012 16:19:12 +0100
> > From: Andreas Herrmann <andreas.herrmann3@amd.com>
> > To: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin"
> > 	<hpa@zytor.com>
> > CC: linux-kernel@vger.kernel.org
> > Subject: [PATCH 1/2] x86/amd: Restore early_fill_mp_bus_to_node
> > 
> > 
> > Once upon a time this function was overloaded with quirky stuff to fix
> > resource detection on systems w/ _CRS defects (seems that some Sun and
> > HP systems were affected).
> > 
> > See commit 30a18d6c3f1e774de656ebd8ff219d53e2ba4029
> > (x86: multi pci root bus with different io resource range, on 64-bit)
> > 
> > Restore the old function and thus decouple it from the quirk that is
> > CPU family specific (e.g. it won't work on AMD family 15h CPUs). BTW,
> > I assume that the _CRS stuff is working on current systems.
> > 
> > This is required to properly initilize the numa_node information of
> > PCI busses and associated devices.
> > 
> > Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com>
> > ---
> >  arch/x86/pci/amd_bus.c |   84 +++++++++++++++++++++++++++++++----------------
> 
> ISTR this function getting things wrong on some Nehalem based systems,
> and assigning all IO devices to node 0, resulting in bad NIC
> performance.

Are you referring to the original early_fill_mp_bus_to_node function?
I don't see how this can happen as it's only called in case of
existence of AMD CPU NB devices. Those won't be detected on Intel at
all.

> Jesse, are things working ok now?  Care to test this patch to make
> sure it doesn't regress anything on one of the previously affected
> systems?




Andreas



  reply	other threads:[~2012-02-28 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120227094406.GB10078@elte.hu>
2012-02-27 20:22 ` [andreas.herrmann3@amd.com: [PATCH 1/2] x86/amd: Restore early_fill_mp_bus_to_node] Jesse Barnes
2012-02-28 17:42   ` Andreas Herrmann [this message]
2012-04-02 17:20   ` [PATCH 1/2] [resend] x86/amd: Restore early_fill_mp_bus_to_node Andreas Herrmann
2012-04-02 17:21     ` [PATCH 2/2] [resend] x86/amd: Enable early_fill_mp_bus_to_node on AMD family 15h models 0-0xf Andreas Herrmann

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=20120228174232.GI31006@alberich.amd.com \
    --to=andreas.herrmann3@amd.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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).