From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Add phenom CPU descriptor
Date: Tue, 27 Jan 2009 08:37:14 -0600 [thread overview]
Message-ID: <497F1C1A.40700@codemonkey.ws> (raw)
In-Reply-To: <1233059726-8566-3-git-send-email-agraf@suse.de>
Alexander Graf wrote:
> As part of my ongoing effort to make nested SVM useful, I started working to get
> VMware ESX run inside KVM.
>
> VMware couples itself pretty tightly to the CPUID, so it's a good idea to emulate
> a machine that officially supports SVM and should thus exploit the powers of
> nested virtualization.
>
> This patch adds a Phenom CPU identifier, that resembles a real-world phenom
> CPU as closely as possible.
>
I didn't apply this last time because I dislike the idea of adding
oodles of CPU definitions for x86. The proper thing to do here is to
have an fdt based description of CPU model. That's not to say I won't
apply this patch, but I don't like the idea of adding more and more of
these things.
Regards,
Anthony Liguori
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
> target-i386/helper.c | 28 ++++++++++++++++++++++++++++
> 1 files changed, 28 insertions(+), 0 deletions(-)
>
> diff --git a/target-i386/helper.c b/target-i386/helper.c
> index c2da767..636a02d 100644
> --- a/target-i386/helper.c
> +++ b/target-i386/helper.c
> @@ -137,6 +137,34 @@ static x86_def_t x86_defs[] = {
> .model_id = "QEMU Virtual CPU version " QEMU_VERSION,
> },
> {
> + .name = "phenom",
> + .level = 5,
> + .vendor1 = CPUID_VENDOR_AMD_1,
> + .vendor2 = CPUID_VENDOR_AMD_2,
> + .vendor3 = CPUID_VENDOR_AMD_3,
> + .family = 16,
> + .model = 2,
> + .stepping = 3,
> + /* Missing: CPUID_VME, CPUID_HT */
> + .features = PPRO_FEATURES |
> + CPUID_MTRR | CPUID_CLFLUSH | CPUID_MCA |
> + CPUID_PSE36,
> + /* Missing: CPUID_EXT_CX16, CPUID_EXT_POPCNT */
> + .ext_features = CPUID_EXT_SSE3 | CPUID_EXT_MONITOR,
> + /* Missing: CPUID_EXT2_PDPE1GB, CPUID_EXT2_RDTSCP */
> + .ext2_features = (PPRO_FEATURES & 0x0183F3FF) |
> + CPUID_EXT2_LM | CPUID_EXT2_SYSCALL | CPUID_EXT2_NX |
> + CPUID_EXT2_3DNOW | CPUID_EXT2_3DNOWEXT | CPUID_EXT2_MMXEXT |
> + CPUID_EXT2_FFXSR,
> + /* Missing: CPUID_EXT3_LAHF_LM, CPUID_EXT3_CMP_LEG, CPUID_EXT3_EXTAPIC,
> + CPUID_EXT3_CR8LEG, CPUID_EXT3_ABM, CPUID_EXT3_SSE4A,
> + CPUID_EXT3_MISALIGNSSE, CPUID_EXT3_3DNOWPREFETCH,
> + CPUID_EXT3_OSVW, CPUID_EXT3_IBS */
> + .ext3_features = CPUID_EXT3_SVM,
> + .xlevel = 0x8000001A,
> + .model_id = "AMD Phenom(tm) 9550 Quad-Core Processor"
> + },
> + {
> .name = "core2duo",
> .level = 10,
> .family = 6,
>
next prev parent reply other threads:[~2009-01-27 14:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 12:35 [Qemu-devel] [PATCH 0/2] Add Phenom CPU Descriptor Alexander Graf
2009-01-27 12:35 ` [Qemu-devel] [PATCH 1/2] Implement FFXSR Alexander Graf
2009-01-27 12:35 ` [Qemu-devel] [PATCH 2/2] Add phenom CPU descriptor Alexander Graf
2009-01-27 14:37 ` Anthony Liguori [this message]
2009-01-27 15:16 ` Alexander Graf
2009-01-27 15:33 ` Laurent Vivier
2009-01-27 19:12 ` Anthony Liguori
2009-01-27 22:39 ` Paul Brook
2009-01-27 22:56 ` Paul Brook
2009-01-28 16:43 ` Jamie Lokier
2009-01-30 9:06 ` Amit Shah
2009-01-28 8:17 ` Alexander Graf
2009-02-02 17:11 ` [Qemu-devel] [PATCH 0/2] Add Phenom CPU Descriptor Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2009-01-05 16:11 [Qemu-devel] [PATCH 0/2] VMware ESX guest bringup (partial) Alexander Graf
2009-01-05 16:11 ` [Qemu-devel] [PATCH 1/2] [RFC] Make vmport report the processor speed Alexander Graf
2009-01-05 16:11 ` [Qemu-devel] [PATCH 2/2] Add phenom CPU descriptor Alexander Graf
2009-01-09 23:16 ` Alexander Graf
2009-01-09 23:36 ` 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=497F1C1A.40700@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).