xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Andre Przywara <andre.przywara@amd.com>,
	Nitin Kamble <nitin.a.kamble@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] libxc: remove CPUID core information mangling
Date: Wed, 25 Aug 2010 13:42:17 +0100	[thread overview]
Message-ID: <C89ACE39.1F0B0%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C7506BA.4000001@amd.com>

On 25/08/2010 13:04, "Andre Przywara" <andre.przywara@amd.com> wrote:

> Hi,
> 
> c/s 18560:782599274bf9ae8857c55856c9c7fdf082967808 introduced CPUID
> mangling resulting in a doubled number of cores/processor exposed to the
> guest. According to comments in this patch the rationale behind this is
> to match the APIC numbering used by Xen.
> In my understanding the CPUID leafs dealing with number of cores always
> talk about logical numbers and not APIC IDs. So we don't need to adjust
> the CPUID readout to match the APIC ID enumeration scheme.
> If there were any serious reasons resulting in the old patch I'd love to
> hear them.
> 
> The attached patch fixes this and solves an issue I saw with certain
> NUMA guest configurations.

I think you shouldn't change handling of 80000008:ECX[15:12] since that does
explicitly refer to APIC ID arrangement. The rest of your changes could be
correct as far as I can tell from the reference manuals.

The intent by the way was to pass through host cores-per-package info so
that software licenses based on #packages would operate correctly in a
virtualised environment. It's pretty hacky though indeed.

 -- Keir

> Signed-off-by: Andre Przywara <andre.przywara@amd.com>

  reply	other threads:[~2010-08-25 12:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 12:04 [PATCH] libxc: remove CPUID core information mangling Andre Przywara
2010-08-25 12:42 ` Keir Fraser [this message]
2010-08-25 15:28   ` Huang2, Wei
2010-08-25 15:39     ` Keir Fraser
2010-08-25 15:53       ` Huang2, Wei
2010-08-25 16:00         ` Keir Fraser
2010-08-26 20:48           ` Andre Przywara
2010-08-25 15:25 ` [osrc-patches] " Huang2, Wei

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=C89ACE39.1F0B0%keir.fraser@eu.citrix.com \
    --to=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 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).