All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [RFC PATCH] kvm: Enable -cpu option to hide KVM
Date: Mon, 02 Jun 2014 09:09:51 +0200	[thread overview]
Message-ID: <538C233F.5030106@redhat.com> (raw)
In-Reply-To: <1401657070.9207.6.camel@ul30vt.home>

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.

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alex Williamson <alex.williamson@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 09:09:51 +0200	[thread overview]
Message-ID: <538C233F.5030106@redhat.com> (raw)
In-Reply-To: <1401657070.9207.6.camel@ul30vt.home>

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.

Paolo

  reply	other threads:[~2014-06-02  7:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 16:25 [RFC PATCH] kvm: Enable -cpu option to hide KVM Alex Williamson
2014-06-01 16:25 ` [Qemu-devel] " Alex Williamson
2014-06-01 18:29 ` Paolo Bonzini
2014-06-01 18:29   ` [Qemu-devel] " Paolo Bonzini
2014-06-01 21:11   ` Alex Williamson
2014-06-01 21:11     ` [Qemu-devel] " Alex Williamson
2014-06-02  7:09     ` Paolo Bonzini [this message]
2014-06-02  7:09       ` Paolo Bonzini
2014-06-02 14:42       ` Alex Williamson
2014-06-02 14:42         ` [Qemu-devel] " Alex Williamson
2014-06-02 15:55         ` Paolo Bonzini
2014-06-02 15:55           ` [Qemu-devel] " Paolo Bonzini
2014-06-02 10:32 ` Michael Tokarev
2014-06-02 10:32   ` [Qemu-devel] " Michael Tokarev
2014-06-02 13:30   ` Alex Williamson
2014-06-02 13:30     ` [Qemu-devel] " Alex Williamson
2014-06-02 15:55     ` Paolo Bonzini
2014-06-02 15:55       ` [Qemu-devel] " Paolo Bonzini
2014-06-02 18:01     ` Michael Tokarev
2014-06-02 18:01       ` [Qemu-devel] " Michael Tokarev
2014-06-02 18:37       ` Alex Williamson
2014-06-02 18:37         ` [Qemu-devel] " Alex Williamson
2014-06-02 19:03       ` Bandan Das
2014-06-02 19:03         ` [Qemu-devel] " Bandan Das
2014-06-02 19:18         ` Alex Williamson
2014-06-02 19:18           ` [Qemu-devel] " 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=538C233F.5030106@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=alex.williamson@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.