From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] x86: fix pv cpuid masking
Date: Wed, 16 Jun 2010 14:21:03 +0100 [thread overview]
Message-ID: <4C18EBDF0200007800006AF8@vpn.id2.novell.com> (raw)
In-Reply-To: <4C1784F8020000780000677C@vpn.id2.novell.com>
>>> On 15.06.10 at 13:49, "Jan Beulich" <JBeulich@novell.com> wrote:
> Invert initial values of the variables parsed into from the command
> line, so that completely clearing out one or more of the four bit
> fields is possible.
>
> Further, consolidate the command line parameter specifications into
> a single place.
>
> Finally, as per "Intel Virtualization Technology FlexMigration
> Application Note" (http://www.intel.com/Assets/PDF/manual/323850.pdf),
> also handle family 6 model 0x1f.
>
> What remains open is the question whether pv_cpuid() shouldn't also
> consume these masks.
What is your opinion on this, Keir?
Jan
next prev parent reply other threads:[~2010-06-16 13:21 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 [this message]
2010-06-16 13:29 ` 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=4C18EBDF0200007800006AF8@vpn.id2.novell.com \
--to=jbeulich@novell.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 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).