From: Paul Durrant <paul.durrant@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Jan Beulich <jbeulich@suse.com>
Subject: [PATCH v4 1/3] x86/viridian: don't put Xen version information in CPUID leaf 2
Date: Wed, 22 Mar 2017 12:15:22 +0000 [thread overview]
Message-ID: <1490184924-20156-2-git-send-email-paul.durrant@citrix.com> (raw)
In-Reply-To: <1490184924-20156-1-git-send-email-paul.durrant@citrix.com>
The Hypervisor Top Level Functional Specification v5.0a states in section
2.5:
"The hypervisor version information is encoded in leaf 0x40000002. Two
version numbers are provided: the main version and the service version.
The main version includes a major and minor version number and a build
number. These correspond to Microsoft Windows release numbers."
It also goes on to advise clients (i.e. guest versions of Windows) to use
the following algorithm to determine compatibility with the hypervisor
enlightenments:
if <your-main-version> greater than <hypervisor-main-version>
{
your version is compatible
}
else if <your-main-version> equal to <hypervisor-main-version> and
<your-service-version> greater than or equal to <hypervisor-service-version>
{
your version is compatible
}
else
{
your version is NOT compatible
}
So, clearly putting Xen hypervisor version information in that leaf is
spurious, but we probably get away with it because Xen's major version
is lower than the major version of Windows in which Hyper-V first
appeared (Server 2008).
This patch changes the leaf to use the kernel major and minor
versions, and build number from Windows Server 2008 (64-bit) by default.
These default values can be overriden from the Xen command line using new
'viridian-version' parameter.
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
---
Cc: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
v4:
- Make elements of viridian-version parameter optional
- Use custom_param()
- Constify a pointer
v3:
- Use a combined version parameter
v2:
- Use full version information (including build number) from Windows
Server 2008
- Add command line parameters to allow version information to be
overridden
---
docs/misc/xen-command-line.markdown | 8 +++++
xen/arch/x86/hvm/viridian.c | 59 +++++++++++++++++++++++++++++++++++--
2 files changed, 65 insertions(+), 2 deletions(-)
diff --git a/docs/misc/xen-command-line.markdown b/docs/misc/xen-command-line.markdown
index bad20db..c81d693 100644
--- a/docs/misc/xen-command-line.markdown
+++ b/docs/misc/xen-command-line.markdown
@@ -1616,6 +1616,14 @@ The optional `keep` parameter causes Xen to continue using the vga
console even after dom0 has been started. The default behaviour is to
relinquish control to dom0.
+### viridian-version
+> `= [<major>],[<minor>],[<build>]`
+
+> Default: `6,0,0x1772`
+
+<major>, <minor> and <build> must be integers. The values will be
+encoded in guest CPUID 0x40000002 if viridian enlightenments are enabled.
+
### vpid (Intel)
> `= <boolean>`
diff --git a/xen/arch/x86/hvm/viridian.c b/xen/arch/x86/hvm/viridian.c
index b740224..3d58416 100644
--- a/xen/arch/x86/hvm/viridian.c
+++ b/xen/arch/x86/hvm/viridian.c
@@ -164,6 +164,16 @@ typedef struct {
#define CPUID6A_MSR_BITMAPS (1 << 1)
#define CPUID6A_NESTED_PAGING (1 << 3)
+/*
+ * Version and build number reported by CPUID leaf 2
+ *
+ * These numbers are chosen to match the version numbers reported by
+ * Windows Server 2008.
+ */
+static uint16_t viridian_major = 6;
+static uint16_t viridian_minor = 0;
+static uint32_t viridian_build = 0x1772;
+
void cpuid_viridian_leaves(const struct vcpu *v, uint32_t leaf,
uint32_t subleaf, struct cpuid_leaf *res)
{
@@ -194,8 +204,8 @@ void cpuid_viridian_leaves(const struct vcpu *v, uint32_t leaf,
own version number. */
if ( d->arch.hvm_domain.viridian.guest_os_id.raw == 0 )
break;
- res->a = 1; /* Build number */
- res->b = (xen_major_version() << 16) | xen_minor_version();
+ res->a = viridian_build;
+ res->b = ((uint32_t)viridian_major << 16) | viridian_minor;
res->c = 0; /* SP */
res->d = 0; /* Service branch and number */
break;
@@ -990,6 +1000,51 @@ static int viridian_load_vcpu_ctxt(struct domain *d, hvm_domain_context_t *h)
HVM_REGISTER_SAVE_RESTORE(VIRIDIAN_VCPU, viridian_save_vcpu_ctxt,
viridian_load_vcpu_ctxt, 1, HVMSR_PER_VCPU);
+static void __init parse_viridian_version(char *arg)
+{
+ const char *t;
+ long n[3];
+ unsigned int i = 0;
+
+ if ( !arg )
+ return;
+
+ while ( (t = strsep(&arg, ",")) != NULL )
+ {
+ const char *e;
+
+ if ( *t == '\0' )
+ {
+ n[i++] = -1;
+ continue;
+ }
+
+ n[i++] = simple_strtoul(t, &e, 0);
+ if ( *e != '\0' )
+ goto fail;
+ }
+ if ( i != 3 )
+ goto fail;
+
+ if ( n[0] > 0xffff || n[1] > 0xffff || n[2] > 0xffffffff )
+ goto fail;
+
+ if ( n[0] >= 0 )
+ viridian_major = n[0];
+ if ( n[1] >= 0 )
+ viridian_minor = n[1];
+ if ( n[2] >= 0 )
+ viridian_build = n[2];
+
+ printk("Overriding viridian-version to %#x,%#x,%#x\n",
+ viridian_major, viridian_minor, viridian_build);
+ return;
+
+fail:
+ printk(XENLOG_WARNING "Invalid viridian-version, using default\n");
+}
+custom_param("viridian-version", parse_viridian_version);
+
/*
* Local variables:
* mode: C
--
2.1.4
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-22 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 12:15 [PATCH v4 0/3] viridian updates Paul Durrant
2017-03-22 12:15 ` Paul Durrant [this message]
2017-03-22 13:55 ` [PATCH v4 1/3] x86/viridian: don't put Xen version information in CPUID leaf 2 Jan Beulich
2017-03-22 14:36 ` Paul Durrant
2017-03-22 12:15 ` [PATCH v4 2/3] x86/viridian: make the threshold for HvNotifyLongSpinWait tunable Paul Durrant
2017-03-22 12:15 ` [PATCH v4 3/3] x86/viridian: implement the crash MSRs Paul Durrant
2017-03-22 12:17 ` Paul Durrant
2017-03-22 12:27 ` 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=1490184924-20156-2-git-send-email-paul.durrant@citrix.com \
--to=paul.durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.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 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).