From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>, Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: KVM call agenda for Jan 26
Date: Tue, 26 Jan 2010 08:32:56 -0600 [thread overview]
Message-ID: <4B5EFD18.1030008@codemonkey.ws> (raw)
In-Reply-To: <4B5EFB7A.7010709@redhat.com>
On 01/26/2010 08:26 AM, Avi Kivity wrote:
> On 01/26/2010 04:22 PM, Anthony Liguori wrote:
>> On 01/26/2010 08:15 AM, Avi Kivity wrote:
>>> On 01/26/2010 04:13 PM, Anthony Liguori wrote:
>>>>> Me too, especially as the whole stack is involved, and qemu is the
>>>>> topmost part from our perspective (no doubt libvirt will want to
>>>>> integrate that functionality as well).
>>>>
>>>>
>>>> I'm not sure I agree. It would use no code from qemu and really
>>>> benefit in no way from being part of qemu. I don't feel that
>>>> strongly about it though.
>>>>
>>>
>>> It would need to know which cpuid bits qemu supports. Only qemu
>>> knows that.
>>
>> I'm not sure I understand why. Can you elaborate?
>>
>
> If qemu doesn't recognize -cpu qemu64,+nx, then no amount of hardware
> and kvm.ko support will allow the user to enable nx in a guest.
Does -cpu host filter out flags that we don't know about? I'm pretty
sure it doesn't. Since we're planning on moving to -cpu host by default
for KVM, does it really matter?
Oh, I was under the impression that the tool was meant to be software
agnostic. IOW, here are all the virt features your hardware supports.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2010-01-26 14:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 6:49 [Qemu-devel] KVM call agenda for Jan 26 Chris Wright
2010-01-26 9:09 ` [Qemu-devel] " Alexander Graf
2010-01-26 13:11 ` Anthony Liguori
2010-01-26 13:17 ` Avi Kivity
2010-01-26 13:18 ` Alexander Graf
2010-01-26 13:24 ` Avi Kivity
2010-01-26 13:33 ` Daniel P. Berrange
2010-01-26 13:37 ` Alexander Graf
2010-01-26 13:45 ` Avi Kivity
2010-01-26 14:13 ` Anthony Liguori
2010-01-26 14:15 ` Avi Kivity
2010-01-26 14:22 ` Anthony Liguori
2010-01-26 14:26 ` Avi Kivity
2010-01-26 14:32 ` Anthony Liguori [this message]
2010-01-26 14:37 ` Avi Kivity
2010-01-26 14:42 ` Alexander Graf
2010-01-26 14:47 ` Avi Kivity
2010-01-26 14:50 ` Alexander Graf
2010-01-26 14:59 ` Anthony Liguori
2010-01-26 14:42 ` Anthony Liguori
2010-01-26 14:44 ` Avi Kivity
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=4B5EFD18.1030008@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=chrisw@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).