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, ian.jackson@eu.citrix.com
Subject: Re: [PATCH v3 3/4] x86/hvm: Add HVM-specific hypervisor CPUID leaf
Date: Fri, 14 Mar 2014 10:41:21 -0400 [thread overview]
Message-ID: <53231511.6030705@oracle.com> (raw)
In-Reply-To: <5322C8840200007800124120@nat28.tlf.novell.com>
On 03/14/2014 04:14 AM, Jan Beulich wrote:
>>>> On 13.03.14 at 19:08, Boris Ostrovsky <boris.ostrovsky@oracle.com> wrote:
>> +void hvm_hypervisor_cpuid_leaf(uint32_t idx, uint32_t sub_idx,
>> + uint32_t *eax, uint32_t *ebx,
>> + uint32_t *ecx, uint32_t *edx)
>> +{
>> + if ( idx != 4 )
>> + return;
> What's the point of this check?
Indeed unnecessary, this is already checked at the caller.
> Why is "idx" being passed in here in
> the first place? With you making use of "sub_idx", there's absolutely
> no reason to expect the need for another leaf to ever get funneled
> into here.
I am passing the arguments directly from cpuid_hypervisor_leaves() which
already has idx and sub_idx and I wasn't sure I can assume that they will be
in eax and ecx (which they currently are).
As for sub_idx, I thought that at some point in the future we we might
use it
so I kept it. But I can drop it since it's rather unlikely.
-boris
next prev parent reply other threads:[~2014-03-14 14:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 18:08 [PATCH v3 0/4] Expose HW APIC virtualization support to HVM guests Boris Ostrovsky
2014-03-13 18:08 ` [PATCH v3 1/4] xen/libxc: Allow changes to hypervisor CPUID leaf from config file Boris Ostrovsky
2014-03-14 8:09 ` Jan Beulich
2014-03-14 15:41 ` Boris Ostrovsky
2014-03-14 15:53 ` Jan Beulich
2014-03-13 18:08 ` [PATCH v3 2/4] x86/hvm: Revert 80ecb40362365ba77e68fc609de8bd3b7208ae19 Boris Ostrovsky
2014-03-13 18:08 ` [PATCH v3 3/4] x86/hvm: Add HVM-specific hypervisor CPUID leaf Boris Ostrovsky
2014-03-14 8:14 ` Jan Beulich
2014-03-14 14:41 ` Boris Ostrovsky [this message]
2014-03-14 14:52 ` Jan Beulich
2014-03-13 18:08 ` [PATCH v3 4/4] x86/hvm: Indicate avaliability of HW support of APIC virtualization to HVM guests Boris Ostrovsky
2014-03-14 1:48 ` Zhang, Yang Z
2014-03-14 13:55 ` Boris Ostrovsky
2014-03-17 0:40 ` Zhang, Yang Z
2014-03-17 17:18 ` Boris Ostrovsky
2014-03-14 8:16 ` 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=53231511.6030705@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 \
/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).