From: Glauber Costa <glommer@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com
Subject: [Qemu-devel] [PATCH 0/3] Enhance kvm cpuid
Date: Wed, 28 Jan 2009 14:02:02 -0500 [thread overview]
Message-ID: <1233169325-5487-1-git-send-email-glommer@redhat.com> (raw)
Hey guys
This is a series that aims at enhancing cpuid capabilities in qemu.
The first patch was already sent to the list, and includes suggestions
by Paul.
The other two gives us the ability to query the host for features that
are possibly non-suported, but present in the exposed qemu machine type.
kvm.h | 1 +
target-i386/kvm.c | 101 +++++++++++++++++++++++++++++++++++++++++++++++------
2 files changed, 91 insertions(+), 11 deletions(-)
next reply other threads:[~2009-01-28 19:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 19:02 Glauber Costa [this message]
2009-01-28 19:02 ` [Qemu-devel] [PATCH 1/3] expose paravirt feature list to cpuid Glauber Costa
2009-01-28 19:02 ` [Qemu-devel] [PATCH 2/3] convert cpuid registration to KVM_SET_CPUID2 Glauber Costa
2009-01-28 19:02 ` [Qemu-devel] [PATCH 3/3] mask out forbidden cpuid features Glauber Costa
2009-01-28 21:36 ` [Qemu-devel] Re: [PATCH 1/3] expose paravirt feature list to cpuid 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=1233169325-5487-1-git-send-email-glommer@redhat.com \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.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).