All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH 2/2] introduce -cpu host target
Date: Tue, 23 Jun 2009 13:04:01 +0300	[thread overview]
Message-ID: <4A40A891.4010606@redhat.com> (raw)
In-Reply-To: <1245707277-769-1-git-send-email-andre.przywara@amd.com>

On 06/23/2009 12:47 AM, Andre Przywara wrote:
> Although the guest's CPUID bits can be controlled in a fine grained way
> in QEMU, a simple way to inject the host CPU is missing. This is handy
> for KVM desktop virtualization, where one wants the guest to support the
> full host feature set.
> Introduce another CPU type called 'host', which will propagate the host's
> CPUID bits to the guest. Problematic bits can still be turned off by using
> the existing syntax (-cpu host,-skinit)
>    

kvm already knows how to filter unknown bits to prevent runtime 
failures.  This is even more important for qemu/tcg, since even simple 
bits which only define new instructions need explicit support in qemu.  
I think -cpu host should default to filtering unsupported bits instead 
of hoping the guest will ignore them or expecting the user to know which 
bits to remove.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [PATCH 2/2] introduce -cpu host target
Date: Tue, 23 Jun 2009 13:04:01 +0300	[thread overview]
Message-ID: <4A40A891.4010606@redhat.com> (raw)
In-Reply-To: <1245707277-769-1-git-send-email-andre.przywara@amd.com>

On 06/23/2009 12:47 AM, Andre Przywara wrote:
> Although the guest's CPUID bits can be controlled in a fine grained way
> in QEMU, a simple way to inject the host CPU is missing. This is handy
> for KVM desktop virtualization, where one wants the guest to support the
> full host feature set.
> Introduce another CPU type called 'host', which will propagate the host's
> CPUID bits to the guest. Problematic bits can still be turned off by using
> the existing syntax (-cpu host,-skinit)
>    

kvm already knows how to filter unknown bits to prevent runtime 
failures.  This is even more important for qemu/tcg, since even simple 
bits which only define new instructions need explicit support in qemu.  
I think -cpu host should default to filtering unsupported bits instead 
of hoping the guest will ignore them or expecting the user to know which 
bits to remove.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-06-23 10:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 21:47 [PATCH 2/2] introduce -cpu host target Andre Przywara
2009-06-22 21:47 ` [Qemu-devel] " Andre Przywara
2009-06-23 10:04 ` Avi Kivity [this message]
2009-06-23 10:04   ` [Qemu-devel] " Avi Kivity
2009-06-24  9:54 ` Avi Kivity
2009-06-24  9:54   ` [Qemu-devel] " Avi Kivity
2009-06-24 11:04   ` Andre Przywara
2009-06-24 11:04     ` [Qemu-devel] " Andre Przywara
2009-06-24 11:26     ` Avi Kivity
2009-06-24 11:26       ` [Qemu-devel] " Avi Kivity
2009-06-25 10:36       ` [PATCH] introduce module parameter for ignoring unknown MSRs accesses Andre Przywara
2009-06-25 10:47         ` Avi Kivity
2009-06-24 16:43     ` [Qemu-devel] Re: [PATCH 2/2] introduce -cpu host target Jamie Lokier
2009-06-24 16:43       ` Jamie Lokier
2009-06-24 17:37   ` Filip Navara
2009-06-24 17:46     ` Avi Kivity
2009-06-24 17:59       ` Filip Navara

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=4A40A891.4010606@redhat.com \
    --to=avi@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=andre.przywara@amd.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.