From: Alex Williamson <alex.williamson@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH] kvm: Enable -cpu option to hide KVM
Date: Mon, 02 Jun 2014 08:42:12 -0600 [thread overview]
Message-ID: <1401720132.9207.42.camel@ul30vt.home> (raw)
In-Reply-To: <538C233F.5030106@redhat.com>
On Mon, 2014-06-02 at 09:09 +0200, Paolo Bonzini wrote:
> Il 01/06/2014 23:11, Alex Williamson ha scritto:
> >> >
> >> > It's really a nit, but I think "kvm=no" is preferrable (more consistent
> >> > with how hyper-v leaves are enabled).
> > Happy to oblige, but I'm not sure what I'm looking for. We enably
> > hyper-v leaves if hyperv_enabled(), which seems to boil down to the kvm
> > kernel supporting KVM_CAP_HYPERV and one or more cpu->hyperv_foo
> > features enabled. What's the commandline option I'm looking for that
> > has some sort of hyper-v=on|off? Thanks,
>
> Same as your "no-kvm", just with the default flipped from false to true.
Ah, easy enough. Do we want to limit the scope a bit by indicating
exactly what is getting disabled, perhaps kvm-msr=on|off? Thanks,
Alex
next prev parent reply other threads:[~2014-06-02 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 16:25 [Qemu-devel] [RFC PATCH] kvm: Enable -cpu option to hide KVM Alex Williamson
2014-06-01 18:29 ` Paolo Bonzini
2014-06-01 21:11 ` Alex Williamson
2014-06-02 7:09 ` Paolo Bonzini
2014-06-02 14:42 ` Alex Williamson [this message]
2014-06-02 15:55 ` Paolo Bonzini
2014-06-02 10:32 ` Michael Tokarev
2014-06-02 13:30 ` Alex Williamson
2014-06-02 15:55 ` Paolo Bonzini
2014-06-02 18:01 ` Michael Tokarev
2014-06-02 18:37 ` Alex Williamson
2014-06-02 19:03 ` Bandan Das
2014-06-02 19:18 ` Alex Williamson
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=1401720132.9207.42.camel@ul30vt.home \
--to=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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).