From: Sheng Yang <sheng@linux.intel.com>
To: qemu-devel@nongnu.org
Cc: Jes.Sorensen@redhat.com, kvm@vger.kernel.org, avi@redhat.com,
Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Use kvm64/kvm32 when running under KVM
Date: Thu, 26 Aug 2010 10:00:27 +0800 [thread overview]
Message-ID: <201008261000.27522.sheng@linux.intel.com> (raw)
In-Reply-To: <1280320944-5560-1-git-send-email-Jes.Sorensen@redhat.com>
On Wednesday 28 July 2010 20:42:22 Jes.Sorensen@redhat.com wrote:
> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>
> This set of patches adds default CPU types to the PC compat
> definitions, and patch #2 sets the CPU type to kvm64/kvm32 when
> running under KVM.
>
> Long term we might want to qdev'ify the CPUs but I think it is better
> to keep it simple for 0.13.
Looks good to me.
Some Windows guest wouldn't enable MSI if it think the processor is too old. So we
need this patchset.
--
regards
Yang, Sheng
> Jes Sorensen (2):
> Set a default CPU type for compat PC machine defs.
> Use kvm32/kvm64 as default CPUs when running under KVM.
>
> hw/boards.h | 1 +
> hw/pc.c | 13 +++++++++++--
> hw/pc_piix.c | 15 +++++++++++++++
> vl.c | 2 ++
> 4 files changed, 29 insertions(+), 2 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Sheng Yang <sheng@linux.intel.com>
To: qemu-devel@nongnu.org
Cc: Jes.Sorensen@redhat.com, Anthony Liguori <aliguori@us.ibm.com>,
avi@redhat.com, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Use kvm64/kvm32 when running under KVM
Date: Thu, 26 Aug 2010 10:00:27 +0800 [thread overview]
Message-ID: <201008261000.27522.sheng@linux.intel.com> (raw)
In-Reply-To: <1280320944-5560-1-git-send-email-Jes.Sorensen@redhat.com>
On Wednesday 28 July 2010 20:42:22 Jes.Sorensen@redhat.com wrote:
> From: Jes Sorensen <Jes.Sorensen@redhat.com>
>
> This set of patches adds default CPU types to the PC compat
> definitions, and patch #2 sets the CPU type to kvm64/kvm32 when
> running under KVM.
>
> Long term we might want to qdev'ify the CPUs but I think it is better
> to keep it simple for 0.13.
Looks good to me.
Some Windows guest wouldn't enable MSI if it think the processor is too old. So we
need this patchset.
--
regards
Yang, Sheng
> Jes Sorensen (2):
> Set a default CPU type for compat PC machine defs.
> Use kvm32/kvm64 as default CPUs when running under KVM.
>
> hw/boards.h | 1 +
> hw/pc.c | 13 +++++++++++--
> hw/pc_piix.c | 15 +++++++++++++++
> vl.c | 2 ++
> 4 files changed, 29 insertions(+), 2 deletions(-)
next prev parent reply other threads:[~2010-08-26 2:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 12:42 [PATCH v2 0/2] Use kvm64/kvm32 when running under KVM Jes.Sorensen
2010-07-28 12:42 ` [Qemu-devel] " Jes.Sorensen
2010-07-28 12:42 ` [PATCH 1/2] Set a default CPU type for compat PC machine defs Jes.Sorensen
2010-07-28 12:42 ` [Qemu-devel] " Jes.Sorensen
2010-07-28 12:42 ` [PATCH 2/2] Use kvm32/kvm64 as default CPUs when running under KVM Jes.Sorensen
2010-07-28 12:42 ` [Qemu-devel] " Jes.Sorensen
2010-07-28 13:49 ` [Qemu-devel] [PATCH v2 0/2] Use kvm64/kvm32 " Markus Armbruster
2010-08-26 2:00 ` Sheng Yang [this message]
2010-08-26 2:00 ` Sheng Yang
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=201008261000.27522.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=Jes.Sorensen@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 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.