From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
eddie.dong@intel.com, xen-devel@lists.xen.org,
jun.nakajima@intel.com, yang.z.zhang@intel.com,
ian.jackson@eu.citrix.com
Subject: Re: [PATCH v6 1/4] xen/libxc: Allow changing max number of hypervisor cpuid leaves
Date: Fri, 21 Mar 2014 11:22:32 -0400 [thread overview]
Message-ID: <532C5938.80402@oracle.com> (raw)
In-Reply-To: <532C578202000078000AF429@nat28.tlf.novell.com>
On 03/21/2014 11:15 AM, Jan Beulich wrote:
>>
>> There are two things you want enforce
>> - limit never becoming zero due to user override (at once taking
>> care of the no override case)
>> You think not having leaf 1 is something we should allow? I can see why
>> 2 perhaps may be omitted.
> If we force the lower limit that can be asked for to 1, leaf 1 will always
> be visible.
Oh, I clearly have issues with reading comprehension (among other
things). Sorry.
-boris
next prev parent reply other threads:[~2014-03-21 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 3:51 [PATCH v6 0/4] Expose HW APIC virtualization support to HVM guests Boris Ostrovsky
2014-03-21 3:51 ` [PATCH v6 1/4] xen/libxc: Allow changing max number of hypervisor cpuid leaves Boris Ostrovsky
2014-03-21 10:54 ` Jan Beulich
2014-03-21 15:13 ` Boris Ostrovsky
2014-03-21 15:15 ` Jan Beulich
2014-03-21 15:22 ` Boris Ostrovsky [this message]
2014-03-21 3:51 ` [PATCH v6 2/4] x86/hvm: Revert 80ecb40362365ba77e68fc609de8bd3b7208ae19 Boris Ostrovsky
2014-03-21 3:51 ` [PATCH v6 3/4] x86/hvm: Add HVM-specific hypervisor CPUID leaf Boris Ostrovsky
2014-03-21 3:51 ` [PATCH v6 4/4] x86/hvm: Indicate avaliability of HW support of APIC virtualization to HVM guests Boris Ostrovsky
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=532C5938.80402@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=eddie.dong@intel.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.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).