xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>
Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 4/6] x86/hvm: Move hvm_funcs.cpuid_intercept() handling into hvm_cpuid()
Date: Wed, 16 Nov 2016 11:40:08 -0500	[thread overview]
Message-ID: <d372fa36-19f6-a2b1-343e-52b2103f8407@oracle.com> (raw)
In-Reply-To: <1479299510-700-5-git-send-email-andrew.cooper3@citrix.com>

On 11/16/2016 07:31 AM, Andrew Cooper wrote:
> @@ -3700,6 +3701,14 @@ void hvm_cpuid(unsigned int input, unsigned int *eax, unsigned int *ebx,
>  
>          *ebx &= hvm_featureset[FEATURESET_e8b];
>          break;
> +
> +    case 0x8000001c:
> +        if ( !(v->arch.xcr0 & XSTATE_LWP) )
> +            *eax = 0;
> +        else if ( cpu_has_svm && cpu_has_lwp )
> +            /* Turn on available bit and other features specified in lwp_cfg. */
> +            *eax = (*edx & v->arch.hvm_svm.guest_lwp_cfg) | 1;
> +        break;
>      }

You don't think this whole case should be under cpu_has_svm (or
X86_VENDOR_AMD)?


-boris



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2016-11-16 16:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16 12:31 [PATCH for-4.9 0/6] Introductory cleanup for CPUID phase 2 work Andrew Cooper
2016-11-16 12:31 ` [PATCH 1/6] xen/x86: Add a helper to calculate family/model/stepping information Andrew Cooper
2016-11-16 12:49   ` Jan Beulich
2016-11-16 12:50     ` Andrew Cooper
2016-11-16 12:31 ` [PATCH 2/6] x86/vpmu: Move vpmu_do_cpuid() handling into {pv, hvm}_cpuid() Andrew Cooper
2016-11-16 12:53   ` Jan Beulich
2016-11-16 13:01     ` Andrew Cooper
2016-11-16 13:34       ` Jan Beulich
2016-11-17  5:21         ` Tian, Kevin
2016-11-17 10:52           ` Jan Beulich
2016-11-16 12:31 ` [PATCH 3/6] x86/vpmu: Remove core2_no_vpmu_ops Andrew Cooper
2016-11-16 13:09   ` Jan Beulich
2016-11-16 16:27   ` Boris Ostrovsky
2016-11-16 17:04     ` Andrew Cooper
2016-11-16 17:09       ` Boris Ostrovsky
2016-11-16 17:08         ` Andrew Cooper
2016-11-17  5:29   ` Tian, Kevin
2016-11-16 12:31 ` [PATCH 4/6] x86/hvm: Move hvm_funcs.cpuid_intercept() handling into hvm_cpuid() Andrew Cooper
2016-11-16 15:20   ` Jan Beulich
2016-11-16 17:07     ` Andrew Cooper
2016-11-17 10:54       ` Jan Beulich
2016-11-16 16:40   ` Boris Ostrovsky [this message]
2016-11-16 17:10     ` Andrew Cooper
2016-11-16 17:34       ` Boris Ostrovsky
2016-11-16 17:34         ` Andrew Cooper
2016-11-16 17:45           ` Boris Ostrovsky
2016-11-17  5:41             ` Tian, Kevin
2016-11-16 12:31 ` [PATCH 5/6] x86/time: Move cpuid_time_leaf() handling into cpuid_hypervisor_leaves() Andrew Cooper
2016-11-16 15:47   ` Jan Beulich
2016-11-16 12:31 ` [PATCH 6/6] x86/hvm: Move hvm_hypervisor_cpuid_leaf() " Andrew Cooper
2016-11-16 15:53   ` Jan Beulich
2016-11-16 17:11     ` Andrew Cooper

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=d372fa36-19f6-a2b1-343e-52b2103f8407@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=suravee.suthikulpanit@amd.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).