From: Jean Guyader <jean.guyader@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH] doc: cpuid example for 686
Date: Tue, 17 Jun 2008 15:53:11 +0100 [thread overview]
Message-ID: <4857CFD7.1060607@eu.citrix.com> (raw)
In-Reply-To: <4857CE6F.5070206@eu.citrix.com>
[-- Attachment #1: Type: text/plain, Size: 190 bytes --]
Jean Guyader wrote:
>
> doc: Describes a generic 686 via the cpuid configure.
>
> Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com>
>
Sorry, I missed the patch.
--
Jean Guyader
[-- Attachment #2: example_cpuid_686.patch --]
[-- Type: text/plain, Size: 1077 bytes --]
diff -r 7e00ebe2b7fd tools/examples/xmexample.hvm
--- a/tools/examples/xmexample.hvm Tue Jun 17 09:36:25 2008 +0100
+++ b/tools/examples/xmexample.hvm Tue Jun 17 15:45:27 2008 +0100
@@ -256,16 +256,16 @@ serial='pty'
#vcpus=5
#
# Downgrade the cpuid to make a better compatibility for migration :
-# Look like a PIII :
-# cpuid = [ '0:eax=0x3',
+# Look like a generic 686 :
+# cpuid = [ '0:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0',
# '1:eax=0x06b1,
# ecx=xxxxxxxxxx0000xx00xxx0000000xx0,
# edx=xx00000xxxxxxx0xxxxxxxxx0xxxxxx',
-# '4:eax=0x3,ebx=0x756e6547,ecx=0x6c65746e,edx=0x49656e69',
-# '0x80000000:eax=0x3,ebx=0x756e6547,ecx=0x6c65746e,edx=0x49656e69']
+# '4:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0',
+# '0x80000000:eax=0x3,ebx=0x0,ecx=0x0,edx=0x0']
# with the highest leaf
# - CPUID.0[EAX] : Set the highest leaf
-# - CPUID.1[EAX] : Pentium III
+# - CPUID.1[EAX] : 686
# - CPUID.1[ECX] : Mask some features
# - CPUID.1[EDX] : Mask some features
# - CPUID.4 : Reply like the highest leaf, in our case CPUID.3
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2008-06-17 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 14:47 [PATCH] doc: cpuid example for 686 Jean Guyader
2008-06-17 14:53 ` Jean Guyader [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=4857CFD7.1060607@eu.citrix.com \
--to=jean.guyader@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.