From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Daniel De Graaf <dgdegra@tycho.nsa.gov>,
Keir Fraser <keir.xen@gmail.com>, Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 8/9] xen/arch/x86: use is_hardware_domain instead of domid == 0
Date: Fri, 12 Apr 2013 17:50:24 +0100 [thread overview]
Message-ID: <51683B50.1070408@citrix.com> (raw)
In-Reply-To: <51683AE1.4090503@citrix.com>
On 12/04/13 17:48, Andrew Cooper wrote:
> On 12/04/13 16:49, Ian Campbell wrote:
>> On Fri, 2013-04-12 at 16:41 +0100, Keir Fraser wrote:
>>> We could get rid of this not-always-faulting-cpuid hack in the
>>> hypervisor altogether, if we could provide a paravirtualised interface
>>> that guarantees access to the real CPUID space, for the toolstack to
>>> use.
>> Doesn't XCP have a patch which allows access to the non-levelled cpuid
>> values for the toolstacks benefit? Andy C CCd...
>>
>>
> XCP/XenServer has a specific patch which records the real CPUID values
> before applying the MSRs for feature masking, which can then subsequently
queried by the toolstack.
(Apologies - I sent mid-sentence)
~Andrew
>
> This allows the toolstack to recalculate the host level parity bits
> correctly whenever a host is added or removed from the pool, without
> suffering the problems of getting into a diminishing subset of features
> as slightly heterogeneous hardware is moved in and out of the pool.
>
> The patch is currently in the state of "Needing to be cleaned up for
> upstream" and is in my todo list (albeit quite far down given some
> recent Xen crashes found during stress testing)
>
> I can up its priority if there is a need for it.
>
> ~Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-04-12 16:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 20:13 [PATCH v2 0/9] Rename/remove IS_PRIV Daniel De Graaf
2013-04-11 20:13 ` [PATCH 1/9] xen/arch/x86: remove IS_PRIV access check bypasses Daniel De Graaf
2013-04-11 20:13 ` [PATCH 2/9] xen/xsm: add hooks for claim Daniel De Graaf
2013-04-11 20:13 ` [PATCH 3/9] hvm: convert access check for nested HVM to XSM Daniel De Graaf
2013-04-11 20:13 ` [PATCH 4/9] xen/arch/x86: remove IS_PRIV_FOR references Daniel De Graaf
2013-04-11 20:13 ` [PATCH 5/9] xen/arch/arm: remove rcu_lock_target_domain_by_id Daniel De Graaf
2013-04-11 20:13 ` [PATCH 6/9] xen: rename IS_PRIV to is_hardware_domain Daniel De Graaf
2013-04-11 20:13 ` [PATCH 7/9] xen: use domid check in is_hardware_domain Daniel De Graaf
2013-04-12 8:00 ` Jan Beulich
2013-04-12 14:11 ` Daniel De Graaf
2013-04-12 14:45 ` Jan Beulich
2013-04-11 20:13 ` [PATCH 8/9] xen/arch/x86: use is_hardware_domain instead of domid == 0 Daniel De Graaf
2013-04-12 8:07 ` Jan Beulich
2013-04-12 14:24 ` Daniel De Graaf
2013-04-12 14:49 ` Jan Beulich
2013-04-12 15:41 ` Keir Fraser
2013-04-12 15:49 ` Ian Campbell
2013-04-12 16:48 ` Andrew Cooper
2013-04-12 16:50 ` Andrew Cooper [this message]
2013-04-11 20:13 ` [PATCH 9/9] IOMMU: " Daniel De Graaf
2013-04-12 8:17 ` [PATCH v2 0/9] Rename/remove IS_PRIV Jan Beulich
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=51683B50.1070408@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=keir.xen@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.