All of lore.kernel.org
 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: Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	Keir Fraser <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] xen/public: Correct the documentation of where the Xen cpuid leaves can be found
Date: Fri, 24 Oct 2014 13:07:21 -0400	[thread overview]
Message-ID: <544A8749.5040706@oracle.com> (raw)
In-Reply-To: <1413919295-6071-1-git-send-email-andrew.cooper3@citrix.com>

On 10/21/2014 03:21 PM, Andrew Cooper wrote:
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> CC: Keir Fraser <keir@xen.org>
> CC: Jan Beulich <JBeulich@suse.com>
> CC: Tim Deegan <tim@xen.org>
> CC: Ian Campbell <Ian.Campbell@citrix.com>
> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>

Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

> ---
>   xen/include/public/arch-x86/cpuid.h |   18 +++++++++++++-----
>   1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/xen/include/public/arch-x86/cpuid.h b/xen/include/public/arch-x86/cpuid.h
> index e57a457..6005dfe 100644
> --- a/xen/include/public/arch-x86/cpuid.h
> +++ b/xen/include/public/arch-x86/cpuid.h
> @@ -30,12 +30,20 @@
>   #ifndef __XEN_PUBLIC_ARCH_X86_CPUID_H__
>   #define __XEN_PUBLIC_ARCH_X86_CPUID_H__
>   
> -/* Xen identification leaves start at 0x40000000. */
> +/*
> + * For compatibility with other hypervisor interfaces, the Xen cpuid leaves
> + * can be found at the first otherwise unused 0x100 aligned boundary starting
> + * from 0x40000000.
> + *
> + * e.g If viridian extensions are enabled for an HVM domain, the Xen cpuid
> + * leaves will start at 0x40000100
> + */
> +
>   #define XEN_CPUID_FIRST_LEAF 0x40000000
>   #define XEN_CPUID_LEAF(i)    (XEN_CPUID_FIRST_LEAF + (i))
>   
>   /*
> - * Leaf 1 (0x40000000)
> + * Leaf 1 (0x40000x00)
>    * EAX: Largest Xen-information leaf. All leaves up to an including @EAX
>    *      are supported by the Xen host.
>    * EBX-EDX: "XenVMMXenVMM" signature, allowing positive identification
> @@ -46,14 +54,14 @@
>   #define XEN_CPUID_SIGNATURE_EDX 0x4d4d566e /* "nVMM" */
>   
>   /*
> - * Leaf 2 (0x40000001)
> + * Leaf 2 (0x40000x01)
>    * EAX[31:16]: Xen major version.
>    * EAX[15: 0]: Xen minor version.
>    * EBX-EDX: Reserved (currently all zeroes).
>    */
>   
>   /*
> - * Leaf 3 (0x40000002)
> + * Leaf 3 (0x40000x02)
>    * EAX: Number of hypercall transfer pages. This register is always guaranteed
>    *      to specify one hypercall page.
>    * EBX: Base address of Xen-specific MSRs.
> @@ -66,7 +74,7 @@
>   #define XEN_CPUID_FEAT1_MMU_PT_UPDATE_PRESERVE_AD  (1u<<0)
>   
>   /*
> - * Leaf 5 (0x40000004)
> + * Leaf 5 (0x40000x04)
>    * HVM-specific features
>    */
>   

      reply	other threads:[~2014-10-24 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 19:21 [PATCH] xen/public: Correct the documentation of where the Xen cpuid leaves can be found Andrew Cooper
2014-10-24 17:07 ` 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=544A8749.5040706@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=keir@xen.org \
    --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.