All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>, elena.ufimtseva@oracle.com
Cc: keir@xen.org, tim@xen.org, xen-devel@lists.xen.org,
	Aravind.Gopalakrishnan@amd.com, suravee.suthikulpanit@amd.com,
	Mukesh Rathor <mukesh.rathor@oracle.com>,
	roger.pau@citrix.com
Subject: Re: [PATCH 6/6] AMD-PVH: enable pvh if requirements met
Date: Tue, 23 Jun 2015 22:34:10 -0400	[thread overview]
Message-ID: <558A1722.9010907@oracle.com> (raw)
In-Reply-To: <55896DA2020000780008849F@mail.emea.novell.com>

On 06/23/2015 08:30 AM, Jan Beulich wrote:
>>>> On 22.06.15 at 18:37, <elena.ufimtseva@oracle.com> wrote:
>> --- a/xen/arch/x86/hvm/svm/svm.c
>> +++ b/xen/arch/x86/hvm/svm/svm.c
>> @@ -1444,6 +1444,9 @@ const struct hvm_function_table * __init
>> start_svm(void)
>>       svm_function_table.hap_capabilities = HVM_HAP_SUPERPAGE_2MB |
>>           ((cpuid_edx(0x80000001) & 0x04000000) ? HVM_HAP_SUPERPAGE_1GB : 0);
>>   
>> +    if ( cpu_has_svm_npt  && cpu_has_svm_decode )
>> +        svm_function_table.pvh_supported = 1;
> If svm_decode indeed is a prereq, then the earlier patch dealing
> with the handle_mmio() invocations doesn't need to fiddle with
> VMEXIT_INVLPG other than to maybe add a documenting ASSERT().
>

I am not sure we should require decode feature to be required for PVH 
support. I can't remember exactly but I think this feature was first 
introduced in family 15h so requiring it will leave at least family 10h 
processors as not supporting PVH.

-boris

  reply	other threads:[~2015-06-24  2:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 16:37 [PATCH 0/6] AMD-PVH: DomU support elena.ufimtseva
2015-06-22 16:37 ` [PATCH 1/6] pvh: domu construct vmcb 64 bit mode start elena.ufimtseva
2015-06-22 19:00   ` Boris Ostrovsky
2015-06-23 12:02   ` Jan Beulich
2015-06-24 20:15     ` Elena Ufimtseva
2015-06-25  8:06       ` Jan Beulich
2015-06-24 20:18     ` Elena Ufimtseva
2015-06-22 16:37 ` [PATCH 2/6] AMD-PVH: cpuid intercept elena.ufimtseva
2015-06-23 12:09   ` Jan Beulich
2015-06-22 16:37 ` [PATCH 3/6] AMD-PVH: call hvm_emulate_one instead of handle_mmio elena.ufimtseva
2015-06-22 19:29   ` Boris Ostrovsky
2015-06-23 12:12   ` Jan Beulich
2015-06-22 16:37 ` [PATCH 4/6] AMD-PVH: Do not get/set vlapic TPR elena.ufimtseva
2015-06-23 12:17   ` Jan Beulich
2015-06-22 16:37 ` [PATCH 5/6] AMD-PVH: Support TSC_MODE_NEVER_EMULATE for PVH elena.ufimtseva
2015-06-22 17:12   ` Konrad Rzeszutek Wilk
2015-06-23 12:23   ` Jan Beulich
2015-06-22 16:37 ` [PATCH 6/6] AMD-PVH: enable pvh if requirements met elena.ufimtseva
2015-06-23 12:30   ` Jan Beulich
2015-06-24  2:34     ` Boris Ostrovsky [this message]
2015-06-24  7:49       ` Jan Beulich
2015-06-24 18:24         ` Andrew Cooper
2015-06-24 20:26           ` Elena Ufimtseva
2015-06-24 21:41             ` Mukesh Rathor
2015-06-25 14:11               ` Elena Ufimtseva
2015-06-23 11:58 ` [PATCH 0/6] AMD-PVH: DomU support 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=558A1722.9010907@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=JBeulich@suse.com \
    --cc=elena.ufimtseva@oracle.com \
    --cc=keir@xen.org \
    --cc=mukesh.rathor@oracle.com \
    --cc=roger.pau@citrix.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=tim@xen.org \
    --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 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.