From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: andre.przywara@amd.com, "Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH 0/4] target-i386: Helpers for CPUID version
Date: Fri, 17 Feb 2012 17:46:00 +0100 [thread overview]
Message-ID: <1329497164-20086-1-git-send-email-afaerber@suse.de> (raw)
Hello x86 gurus,
This series came out of my qom-cpu work. The reasoning is that in a QOM world
we will need this logic twice, once as before and once for
-cpu family=x,model=y,stepping=z,model_id=foo.
Note: The family=x value is not bounds-checked in cpu_x86_find_by_name()!
I'd appreciate if someone could double-check the masks I added. I calculated
them based on "Intel® Processor Identification and the CPUID Instruction.
Application Note 485. January 2011".
Thanks,
Andreas
Cc: Andre Przywara <andre.przywara@amd.com>
Andreas Färber (4):
target-i386: Introduce x86_cpuid_version_set_family()
target-i386: Introduce x86_cpuid_version_set_model()
target-i386: Introduce x86_cpuid_version_set_stepping()
target-i386: Introduce x86_cpuid_set_model_id()
target-i386/cpuid.c | 64 +++++++++++++++++++++++++++++++++++----------------
1 files changed, 44 insertions(+), 20 deletions(-)
--
1.7.7
next reply other threads:[~2012-02-17 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 16:46 Andreas Färber [this message]
2012-02-17 16:46 ` [Qemu-devel] [PATCH 1/4] target-i386: Introduce x86_cpuid_version_set_family() Andreas Färber
2012-02-17 16:46 ` [Qemu-devel] [PATCH 2/4] target-i386: Introduce x86_cpuid_version_set_model() Andreas Färber
2012-02-17 16:46 ` [Qemu-devel] [PATCH 3/4] target-i386: Introduce x86_cpuid_version_set_stepping() Andreas Färber
2012-02-17 16:46 ` [Qemu-devel] [PATCH 4/4] target-i386: Introduce x86_cpuid_set_model_id() Andreas Färber
2012-02-24 15:31 ` [Qemu-devel] [PATCH 0/4] target-i386: Helpers for CPUID version 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=1329497164-20086-1-git-send-email-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=andre.przywara@amd.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).