From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] xen: disable reporting hw virtualized lapic availability on PVH guests
Date: Wed, 4 Jun 2014 12:53:37 +0200 [thread overview]
Message-ID: <538EFAB1.3030503@citrix.com> (raw)
In-Reply-To: <538F14E40200007800017B18@mail.emea.novell.com>
On 04/06/14 12:45, Jan Beulich wrote:
>>>> On 04.06.14 at 12:12, <roger.pau@citrix.com> wrote:
>> --- a/xen/arch/x86/hvm/vmx/vmx.c
>> +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> @@ -1660,7 +1660,7 @@ 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 )
>> + if ( sub_idx != 0 || is_pvh_vcpu(current) )
>> return;
>> if ( cpu_has_vmx_apic_reg_virt )
>
> The addition would belong on this line imo (in the && !is_pvh form).
Then I would also have to add another is_pvh gate on the next if:
if ( cpu_has_vmx_virtualize_x2apic_mode && cpu_has_vmx_apic_reg_virt &&
cpu_has_vmx_virtual_intr_delivery && !is_pvh_vcpu(current) )
*eax |= XEN_HVM_CPUID_X2APIC_VIRT;
IMHO it seems easier to gate it on the first if and just
return, although I understand it is more correct to gate
it on a feature by feature basis.
Roger.
next prev parent reply other threads:[~2014-06-04 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 10:12 [PATCH] xen: disable reporting hw virtualized lapic availability on PVH guests Roger Pau Monne
2014-06-04 10:45 ` Jan Beulich
2014-06-04 10:53 ` Roger Pau Monné [this message]
2014-06-04 12:13 ` 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=538EFAB1.3030503@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.