From: Amit Shah <amit.shah@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, avi@redhat.com, kvm@vger.kernel.org
Subject: [Qemu-devel] v3: KVM: support for 'count' in CPUID functions 4, 0xb and 0xd
Date: Wed, 14 Jan 2009 16:41:08 +0000 [thread overview]
Message-ID: <1231951270-23664-1-git-send-email-amit.shah@redhat.com> (raw)
These patches add support for cpuid functions that take a 'count' parameter
in addition to the function number. With these patches, KVM can run a VM
started with a newer CPU type (coreduo, core2duo). These patches also pave
way for a "host" CPU type, where we could pass the CPU type of the current
host to the VM.
v3 uses the as-yet unused KVM_SET_CPUID2 interface, which was written to
support this functionality. Since we rely on kernel versions 2.6.25 at a
minimum for KVM and the SET_CPUID2 interface was introduced in 2.6.25, we're
safe with this.
Please apply.
next reply other threads:[~2009-01-14 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 16:41 Amit Shah [this message]
2009-01-14 16:41 ` [Qemu-devel] [PATCH 1/2] KVM: CPUID takes ecx as input value for some functions Amit Shah
2009-01-14 16:41 ` [Qemu-devel] [PATCH 2/2] KVM: Fetch sub-leaf cpuid values for functions 4, 0xb, 0xd Amit Shah
2009-01-15 21:54 ` [Qemu-devel] Re: [PATCH 1/2] KVM: CPUID takes ecx as input value for some functions Anthony Liguori
2009-01-16 11:17 ` [Qemu-devel] KVM: support for 'count' in CPUID functions 4, 0xb and 0xd Amit Shah
2009-01-16 11:17 ` [Qemu-devel] [PATCH 1/2] KVM: CPUID takes ecx as input value for some functions Amit Shah
2009-01-16 11:17 ` [Qemu-devel] [PATCH 2/2] KVM: Fetch sub-leaf cpuid values for functions 4, 0xb, 0xd Amit Shah
2009-01-15 9:54 ` [Qemu-devel] Re: v3: KVM: support for 'count' in CPUID functions 4, 0xb and 0xd Avi Kivity
2009-01-15 10:28 ` Amit Shah
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=1231951270-23664-1-git-send-email-amit.shah@redhat.com \
--to=amit.shah@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@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).