All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Nitin A Kamble <nitin.a.kamble@intel.com>
Cc: Andre Przywara <andre.przywara@amd.com>,
	xen-devel@lists.xensource.com,
	Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: c/s 21118: Magny-Coure breakage
Date: Mon, 12 Apr 2010 12:07:24 +0200	[thread overview]
Message-ID: <201004121207.25060.Christoph.Egger@amd.com> (raw)


Hi!

Changeset 21118 breaks NUMA on AMD Magny-Coure due to introduction of
'sockets_per_node'. On AMD Magny-Coure we have two nodes on one socket, hence
the existence of that field member introduces a breake on design level.

Please revert changeset 21118 or rework the patch to get rid of this field 
member.

Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Andrew Bowd, Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

             reply	other threads:[~2010-04-12 10:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 10:07 Christoph Egger [this message]
2010-04-12 10:41 ` c/s 21118: Magny-Coure breakage Keir Fraser
2010-04-12 11:00   ` Keir Fraser
2010-04-12 12:48     ` Dan Magenheimer
2010-04-12 13:14       ` Andre Przywara
2010-04-12 13:24         ` Keir Fraser
2010-04-12 18:28           ` Kamble, Nitin A
2010-04-14  9:46             ` Andre Przywara
2010-04-14 17:13               ` Kamble, Nitin A
2010-04-15 11:33                 ` [PATCH] xend: make NUMA in xm info optional Andre Przywara
2010-04-15 12:11                   ` Keir Fraser
2010-04-15 12:14                     ` Andre Przywara
2010-04-15 12:19                       ` Keir Fraser

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=201004121207.25060.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=andre.przywara@amd.com \
    --cc=nitin.a.kamble@intel.com \
    --cc=xen-devel@lists.xensource.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 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.