All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Keir Fraser <keir@xen.org>, Elena Ufimtseva <ufimtseva@gmail.com>,
	Jan Beulich <JBeulich@suse.com>,
	Eric Shelton <eshelton@pobox.com>
Subject: Re: What is the target CPU "topology" of an SMP HVM machine?
Date: Wed, 14 Aug 2013 22:52:54 +0200	[thread overview]
Message-ID: <1376513574.2687.191.camel@Abyss> (raw)
In-Reply-To: <520BE333.8040201@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1544 bytes --]

On mer, 2013-08-14 at 21:06 +0100, Andrew Cooper wrote:
> On 14/08/13 20:23, Eric Shelton wrote:
> > So, seeing as this information is being closely interrogated, what is
> > the target virtual CPU topology?  How should this be reported via
> > CPUID and MSR?  Darwin appears to be trying to determine or take into
> > account things such as a number of packages, dies per package, cores
> > per pie & package, and threads/logical CPUs per core & package; the
> > degrees of sharing of caches by CPUs at various cache levels, and the
> > presence of hyperthreading.
> 
> Xen by default advertises all VCPUs as separate sockets, to try and
> dissuade "clever" schedulers from doing dumb things based on false
> information.
> 
Are we absolutely sure about this? I'm asking because Elena run into a
similar issue, i.e., seeing some vCPUs being advertised as
threads/siblings (although that was a pv-guest)... Am I right Elena?

I think she also has a patch that she may be able to share soon, which
does right the masking of some of the CPUID stuff, as it looks like some
false information was reaching out to the Linux Scheduler! :-O

I'm not sure this is the exact same issue, though.... Elena, could you
tell something more about this?

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2013-08-14 20:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 19:23 What is the target CPU "topology" of an SMP HVM machine? Eric Shelton
2013-08-14 20:06 ` Andrew Cooper
2013-08-14 20:52   ` Dario Faggioli [this message]
2013-08-15  2:18     ` Elena Ufimtseva
2013-08-21 21:30     ` Matt Wilson
2013-08-14 22:59   ` Eric Shelton

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=1376513574.2687.191.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=eshelton@pobox.com \
    --cc=keir@xen.org \
    --cc=ufimtseva@gmail.com \
    --cc=xen-devel@lists.xen.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.