From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] x86: fix pv cpuid masking
Date: Wed, 16 Jun 2010 14:29:38 +0100 [thread overview]
Message-ID: <C83E9052.17ABC%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C18EBDF0200007800006AF8@vpn.id2.novell.com>
On 16/06/2010 14:21, "Jan Beulich" <JBeulich@novell.com> wrote:
>> What remains open is the question whether pv_cpuid() shouldn't also
>> consume these masks.
>
> What is your opinion on this, Keir?
Libxc/xc_cpuid_x86.c already applies the policy expressed in a domain's
config file, plus its own internal policy, on top of physical host CPUID.
Since host CPUID is already affected by the above-mentioned masks, I don't
think anything further needs to be done.
-- Keir
prev parent reply other threads:[~2010-06-16 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 11:49 [PATCH] x86: fix pv cpuid masking Jan Beulich
2010-06-16 13:21 ` Jan Beulich
2010-06-16 13:29 ` Keir Fraser [this message]
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=C83E9052.17ABC%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.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).