All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
	xen-devel@lists.xensource.com,
	Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Re: c/s 21118: Magny-Coure breakage
Date: Mon, 12 Apr 2010 15:14:16 +0200	[thread overview]
Message-ID: <4BC31CA8.9030404@amd.com> (raw)
In-Reply-To: <2b65e57c-ff10-4d40-a06c-94d738a6e011@default>

Dan Magenheimer wrote:
> A large number of software licensing beancounters in the industry
> are going to be busy on this one ;-)
Yes, but do they use the Xen hypervisor interface for that? And do they 
look at the actual socket number? As far as I remember some companies 
;-) are counting MCMs twice, so actually counting the nodes?

> Christophe, can you comment on how Linux and/or other bare metal
> operating systems will be reporting the Magny Cours hierarchy?
As long as there is no such notion as 'sockets per node' (which isn't on 
Linux), everything is fine. It will just report 8 nodes with 6 cores 
each (in case of a 4 socket M-C). Each core has a associated physical 
package id, which is just the same for 12 cores or 2 nodes.
I have a machine here up and running, so just tell me what sysfs path 
you are interested in and I can send you the output.

> I'd hope that Xen could follow their lead on this rather
> than forge new ground, which may result in an incompatible
> implementation.
Until c/s 21118 Xen was just fine, reporting 8 nodes, 4 sockets and 48 
cores. It is just this socket per node (which got removed some years 
ago), which is doing harm. (BTW: I already complained about that last 
year, when Nitin's patch first appeared on the ML).

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12

  reply	other threads:[~2010-04-12 13:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 10:07 c/s 21118: Magny-Coure breakage Christoph Egger
2010-04-12 10:41 ` Keir Fraser
2010-04-12 11:00   ` Keir Fraser
2010-04-12 12:48     ` Dan Magenheimer
2010-04-12 13:14       ` Andre Przywara [this message]
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=4BC31CA8.9030404@amd.com \
    --to=andre.przywara@amd.com \
    --cc=Christoph.Egger@amd.com \
    --cc=dan.magenheimer@oracle.com \
    --cc=keir.fraser@eu.citrix.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.