From: Amit Shah <amit.shah@redhat.com>
To: qemu-devel@nongnu.org
Cc: Amit Shah <amit.shah@redhat.com>
Subject: [Qemu-devel] [PATCH 2/4] Add independent cpu definitions for the coreduo and core2duo cpu types
Date: Wed, 11 Feb 2009 18:45:12 +0530 [thread overview]
Message-ID: <1234358114-23390-3-git-send-email-amit.shah@redhat.com> (raw)
In-Reply-To: <1234358114-23390-2-git-send-email-amit.shah@redhat.com>
Add these cpu definitions in a separate file which facilitates them to
be modified and updated without having to recompile. New definitions
can also be added without the need to recompile.
The support to actually use these files comes from the patches that
follow in this series
Signed-off-by: Amit Shah <amit.shah@redhat.com>
---
qemu/target-i386/cpudefs/core2duo | 18 ++++++++++++++++++
qemu/target-i386/cpudefs/coreduo | 15 +++++++++++++++
2 files changed, 33 insertions(+), 0 deletions(-)
create mode 100644 qemu/target-i386/cpudefs/core2duo
create mode 100644 qemu/target-i386/cpudefs/coreduo
diff --git a/qemu/target-i386/cpudefs/core2duo b/qemu/target-i386/cpudefs/core2duo
new file mode 100644
index 0000000..b794e78
--- /dev/null
+++ b/qemu/target-i386/cpudefs/core2duo
@@ -0,0 +1,18 @@
+level 10
+family 6
+model 15
+stepping 11
+
+# The original CPU also implements these features:
+# vme dts acpi ss ht tm pbe
+
+features ppro_features mtrr clflush mca pse36 pni monitor ssse3 lm syscall nx
+
+# The original CPU also implements these ext features:
+# CPUID_EXT_DTES64, ds_cpl vmx est tm2 cx16 xtpr CPUID_EXT_PDCM
+
+# The original CPU also implements these ext3 features:
+# lahf_lm
+
+xlevel 0x80000008
+model_id "Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz"
diff --git a/qemu/target-i386/cpudefs/coreduo b/qemu/target-i386/cpudefs/coreduo
new file mode 100644
index 0000000..4ee95da
--- /dev/null
+++ b/qemu/target-i386/cpudefs/coreduo
@@ -0,0 +1,15 @@
+level 10
+family 6
+model 14
+stepping 8
+
+# The original CPU also implements these features:
+# dts acpi ss ht tm pbe
+
+features ppro_features vme mtrr clflush mca pni monitor nx
+
+# The original CPU also implements these ext features:
+# vmx est tm2 xtpr CPUID_EXT_PDCM
+
+xlevel 0x80000008,
+model_id "Genuine Intel(R) CPU T2600 @ 2.16GHz"
--
1.6.0.6
next prev parent reply other threads:[~2009-02-11 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 13:15 [Qemu-devel] Support for out-of-code cpu definitions Amit Shah
2009-02-11 13:15 ` [Qemu-devel] [PATCH 1/4] Introduce get_datafile_dir() to replace bios_dir Amit Shah
2009-02-11 13:15 ` Amit Shah [this message]
2009-02-11 13:15 ` [Qemu-devel] [PATCH 3/4] Update Makefile to copy the cpudef files to install location Amit Shah
2009-02-11 13:15 ` [Qemu-devel] [PATCH 4/4] Support for cpudef files placed in the share/ directory Amit Shah
2009-02-11 15:11 ` [Qemu-devel] Support for out-of-code cpu definitions Blue Swirl
2009-02-11 15:21 ` 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=1234358114-23390-3-git-send-email-amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--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).