From: Avi Kivity <avi@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
kvm@vger.kernel.org, "Daniel P. Berrange" <berrange@redhat.com>,
"Richard W. M. Jones" <rjones@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH] qemu-kvm: Switch to upstream -enable-kvm semantics
Date: Tue, 21 Dec 2010 17:48:39 +0200 [thread overview]
Message-ID: <4D10CC57.3050900@redhat.com> (raw)
In-Reply-To: <m362unkub4.fsf@blackfin.pond.sub.org>
On 12/21/2010 05:41 PM, Markus Armbruster wrote:
> Avi Kivity<avi@redhat.com> writes:
>
> > On 12/15/2010 07:57 PM, Markus Armbruster wrote:
> >> > In the short term, it would be a good idea to modify qemu-kvm to
> >> > switch the -enable-kvm semantics to match upstream (fail if KVM isn't
> >> > available).
> >>
> >> That's what my patch does.
> >>
> >> Additionally, it changes the default to match upstream: KVM disabled.
> >>
> >> What do you want changed in my patch?
> >
> > The 'Additionally' bit. qemu-kvm users rely on the default enabling
> > kvm. Likely they don't rely on -enable-kvm failing is kvm is not
> > available (and indeed, they likely expect it to match upstream). So
> > the patch should only change behaviour when -enable-kvm is specified.
>
> Like this?
>
> upstream qemu | default |-enable-kvm
> ----------------+-----------+-----------
> KVM available | disabled | enabled
> KVM unavailable | disabled | fail
>
> qemu-kvm | default |-enable-kvm| -no-kvm
> ----------------+-----------+-----------+-----------
> KVM available | enabled* | enabled | disabled
> KVM unavailable | disabled | fail | disabled
>
> * differs from upstream
Yes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-21 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 15:50 [PATCH] qemu-kvm: Switch to upstream -enable-kvm semantics Markus Armbruster
2010-12-15 17:31 ` Anthony Liguori
2010-12-15 17:57 ` Markus Armbruster
2010-12-21 15:16 ` Avi Kivity
2010-12-21 15:41 ` Markus Armbruster
2010-12-21 15:48 ` Avi Kivity [this message]
2010-12-21 16:05 ` Markus Armbruster
2010-12-21 16:00 ` Richard W.M. Jones
2010-12-21 16:02 ` Richard W.M. Jones
2010-12-21 16:07 ` Markus Armbruster
2010-12-21 16:56 ` [Qemu-devel] " Anthony Liguori
2010-12-21 17:25 ` Alexander Graf
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=4D10CC57.3050900@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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.