All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [PATCH 0/4] Fix kvm cpuid reporting
Date: Sun,  3 May 2009 17:04:00 +0300	[thread overview]
Message-ID: <1241359444-8538-1-git-send-email-avi@redhat.com> (raw)

kvm supports an interface for reporting which cpuid features are supported.
Use it for trimming the cpu feature set reported to the guest.  This prevents,
for example, reporting NX to a guest when in fact we do not support it.

Avi Kivity (4):
  kvm: Add support for querying supported cpu features
  Make x86 cpuid feature names available in file scope
  Fix x86 feature modifications for features that set multiple bits
  kvm: Trim cpu features not supported by kvm

 kvm.h                |    3 ++
 target-i386/helper.c |   98 +++++++++++++++++++++++++++++++++----------------
 target-i386/kvm.c    |   80 ++++++++++++++++++++++++++++++++++++++++
 3 files changed, 149 insertions(+), 32 deletions(-)


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH 0/4] Fix kvm cpuid reporting
Date: Sun,  3 May 2009 17:04:00 +0300	[thread overview]
Message-ID: <1241359444-8538-1-git-send-email-avi@redhat.com> (raw)

kvm supports an interface for reporting which cpuid features are supported.
Use it for trimming the cpu feature set reported to the guest.  This prevents,
for example, reporting NX to a guest when in fact we do not support it.

Avi Kivity (4):
  kvm: Add support for querying supported cpu features
  Make x86 cpuid feature names available in file scope
  Fix x86 feature modifications for features that set multiple bits
  kvm: Trim cpu features not supported by kvm

 kvm.h                |    3 ++
 target-i386/helper.c |   98 +++++++++++++++++++++++++++++++++----------------
 target-i386/kvm.c    |   80 ++++++++++++++++++++++++++++++++++++++++
 3 files changed, 149 insertions(+), 32 deletions(-)

             reply	other threads:[~2009-05-03 14:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03 14:04 Avi Kivity [this message]
2009-05-03 14:04 ` [Qemu-devel] [PATCH 0/4] Fix kvm cpuid reporting Avi Kivity
2009-05-03 14:04 ` [PATCH 1/4] kvm: Add support for querying supported cpu features Avi Kivity
2009-05-03 14:04   ` [Qemu-devel] " Avi Kivity
2009-05-08 20:50   ` Anthony Liguori
2009-05-08 20:50     ` [Qemu-devel] " Anthony Liguori
2009-05-08 21:09     ` Anthony Liguori
2009-05-08 21:09       ` [Qemu-devel] " Anthony Liguori
2009-05-09  8:41       ` Avi Kivity
2009-05-09  8:41         ` [Qemu-devel] " Avi Kivity
2009-05-03 14:04 ` [PATCH 2/4] Make x86 cpuid feature names available in file scope Avi Kivity
2009-05-03 14:04   ` [Qemu-devel] " Avi Kivity
2009-05-03 14:04 ` [PATCH 3/4] Fix x86 feature modifications for features that set multiple bits Avi Kivity
2009-05-03 14:04   ` [Qemu-devel] " Avi Kivity
2009-05-03 14:04 ` [PATCH 4/4] kvm: Trim cpu features not supported by kvm Avi Kivity
2009-05-03 14:04   ` [Qemu-devel] " Avi Kivity
2009-05-12 11:52   ` Mark McLoughlin
2009-05-12 11:52     ` Mark McLoughlin

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=1241359444-8538-1-git-send-email-avi@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.