From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Glauber Costa <glommer@redhat.com>, Avi Kivity <avi@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: [Qemu-devel] [PATCH 1/3] Add additional CPU flag definitions
Date: Tue, 28 Oct 2008 15:13:32 -0500 [thread overview]
Message-ID: <1225224814-9875-1-git-send-email-aliguori@us.ibm.com> (raw)
Some x86 CPU definitions that KVM needs
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
diff --git a/target-i386/cpu.h b/target-i386/cpu.h
index 3c11e0f..b1678ef 100644
--- a/target-i386/cpu.h
+++ b/target-i386/cpu.h
@@ -159,9 +159,11 @@
#define HF_MP_MASK (1 << HF_MP_SHIFT)
#define HF_EM_MASK (1 << HF_EM_SHIFT)
#define HF_TS_MASK (1 << HF_TS_SHIFT)
+#define HF_IOPL_MASK (3 << HF_IOPL_SHIFT)
#define HF_LMA_MASK (1 << HF_LMA_SHIFT)
#define HF_CS64_MASK (1 << HF_CS64_SHIFT)
#define HF_OSFXSR_MASK (1 << HF_OSFXSR_SHIFT)
+#define HF_VM_MASK (1 << HF_VM_SHIFT)
#define HF_SMM_MASK (1 << HF_SMM_SHIFT)
#define HF_SVME_MASK (1 << HF_SVME_SHIFT)
#define HF_SVMI_MASK (1 << HF_SVMI_SHIFT)
@@ -178,6 +180,9 @@
#define HF2_NMI_MASK (1 << HF2_NMI_SHIFT)
#define HF2_VINTR_MASK (1 << HF2_VINTR_SHIFT)
+#define CR0_PE_SHIFT 0
+#define CR0_MP_SHIFT 1
+
#define CR0_PE_MASK (1 << 0)
#define CR0_MP_MASK (1 << 1)
#define CR0_EM_MASK (1 << 2)
@@ -196,7 +201,8 @@
#define CR4_PAE_MASK (1 << 5)
#define CR4_PGE_MASK (1 << 7)
#define CR4_PCE_MASK (1 << 8)
-#define CR4_OSFXSR_MASK (1 << 9)
+#define CR4_OSFXSR_SHIFT 9
+#define CR4_OSFXSR_MASK (1 << CR4_OSFXSR_SHIFT)
#define CR4_OSXMMEXCPT_MASK (1 << 10)
#define PG_PRESENT_BIT 0
@@ -229,6 +235,7 @@
#define PG_ERROR_RSVD_MASK 0x08
#define PG_ERROR_I_D_MASK 0x10
+#define MSR_IA32_TSC 0x10
#define MSR_IA32_APICBASE 0x1b
#define MSR_IA32_APICBASE_BSP (1<<8)
#define MSR_IA32_APICBASE_ENABLE (1<<11)
next reply other threads:[~2008-10-28 20:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 20:13 Anthony Liguori [this message]
2008-10-28 20:13 ` [Qemu-devel] [PATCH 2/3] Split CPUID from op_helper Anthony Liguori
2008-10-28 20:13 ` [Qemu-devel] [PATCH 3/3] Add KVM support to QEMU Anthony Liguori
2008-10-28 20:49 ` Hollis Blanchard
2008-10-28 21:10 ` Anthony Liguori
2008-10-28 20:57 ` Andreas Färber
2008-10-28 21:04 ` Glauber Costa
2008-10-28 21:16 ` Anthony Liguori
2008-10-28 21:05 ` Anthony Liguori
2008-11-04 13:25 ` Avi Kivity
2008-10-28 21:41 ` [Qemu-devel] " Gerd Hoffmann
2008-10-28 21:51 ` Anthony Liguori
2008-10-28 23:04 ` Glauber Costa
2008-10-28 23:36 ` Anthony Liguori
2008-10-29 9:54 ` Avi Kivity
2008-10-29 12:35 ` Glauber Costa
2008-10-29 12:39 ` Avi Kivity
2008-10-29 12:56 ` Glauber Costa
2008-10-29 13:07 ` Anthony Liguori
2008-10-29 13:23 ` Avi Kivity
2008-10-29 13:32 ` Anthony Liguori
2008-10-29 13:51 ` Hollis Blanchard
2008-10-29 14:09 ` Avi Kivity
2008-10-29 14:16 ` Fabrice Bellard
2008-10-29 14:23 ` Anthony Liguori
2008-10-29 19:13 ` Blue Swirl
2008-11-01 16:25 ` Blue Swirl
2008-10-29 14:58 ` Glauber Costa
2008-10-29 17:41 ` Glauber Costa
2008-10-29 19:01 ` Anthony Liguori
2008-11-04 13:24 ` Avi Kivity
2008-11-04 14:02 ` Anthony Liguori
2008-11-04 14:46 ` Avi Kivity
2008-11-04 14:50 ` Anthony Liguori
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=1225224814-9875-1-git-send-email-aliguori@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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).