From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, ian.campbell@citrix.com,
stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
eddie.dong@intel.com, xen-devel@lists.xen.org,
yang.z.zhang@intel.com, ian.jackson@eu.citrix.com
Subject: Re: [PATCH v9 3/3] x86/hvm: Indicate avaliability of HW support of APIC virtualization to HVM guests
Date: Wed, 23 Apr 2014 09:27:53 -0400 [thread overview]
Message-ID: <5357BFD9.6050206@oracle.com> (raw)
In-Reply-To: <5357A781020000780000B44E@nat28.tlf.novell.com>
On 04/23/2014 05:44 AM, Jan Beulich wrote:
>>>> On 22.04.14 at 21:17, <boris.ostrovsky@oracle.com> wrote:
>> +void vmx_hypervisor_cpuid_leaf(uint32_t sub_idx,
>> + uint32_t *eax, uint32_t *ebx,
>> + uint32_t *ecx, uint32_t *edx)
>> +{
>> + if ( sub_idx != 0 )
>> + return;
>> +printk("cpu_has_vmx_apic_reg_virt=0x%x
>> cpu_has_vmx_virtualize_x2apic_mode=0x%x cpu_has_vmx_apic_reg_virt=0x%x
>> cpu_has_vmx_virtual_intr_delivery=0x%x\n", cpu_has_vmx_apic_reg_virt,
>> cpu_has_vmx_virtualize_x2apic_mode, cpu_has_vmx_apic_reg_virt,
>> cpu_has_vmx_virtual_intr_delivery);
> Urgh?!
>
> Jan
>
<blush>
I'll fix this after Intel folks comment on this patch.
-boris
prev parent reply other threads:[~2014-04-23 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 19:17 [PATCH v9 0/3] Expose HW APIC virtualization support to HVM guests Boris Ostrovsky
2014-04-22 19:17 ` [PATCH v9 1/3] xen/libxc: Allow changing max number of hypervisor cpuid leaves Boris Ostrovsky
2014-04-23 8:42 ` Ian Campbell
2014-04-23 9:46 ` Jan Beulich
2014-04-24 0:36 ` Zhang, Yang Z
2014-05-06 15:23 ` Boris Ostrovsky
2014-05-06 15:35 ` Jan Beulich
2014-04-22 19:17 ` [PATCH v9 2/3] x86/hvm: Add HVM-specific hypervisor CPUID leaf Boris Ostrovsky
2014-04-22 19:17 ` [PATCH v9 3/3] x86/hvm: Indicate avaliability of HW support of APIC virtualization to HVM guests Boris Ostrovsky
2014-04-23 9:44 ` Jan Beulich
2014-04-23 13:27 ` Boris Ostrovsky [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=5357BFD9.6050206@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=kevin.tian@intel.com \
--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).