From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alexander Graf <agraf@suse.de>
Cc: Avi Kivity <avi@redhat.com>, Glauber Costa <glommer@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] exit if we fail to initialize kvm
Date: Wed, 29 Jul 2009 16:43:11 +0200 [thread overview]
Message-ID: <4A705FFF.5060503@siemens.com> (raw)
In-Reply-To: <4A70406B.3050000@suse.de>
Alexander Graf wrote:
> Avi Kivity wrote:
>> On 07/29/2009 01:17 PM, Jan Kiszka wrote:
>>> I just wonder now if/when qemu-kvm will switch over to the
>>> kvm-by-default-off policy of upstream?
>>>
>> That will surely inconvenience/surprise a lot of users.
>>
>> A migration path could be:
>>
>> - add -accel
>> - start warning when -accel is not used, encouraging people to use -accel
>> - time passes
>> - switch default to tcg (maybe unless invoked with kvm in argv[0])
>> - time passes
>> - remove warning
>>
>
> I would prefer:
>
> - add -accel (default to kvm)
> - give a message to use -accel tcg when the user wants tcg
> - make -accel go kvm,kqemu,tcg in qemu upstream
Upstream just dropped the behavior '-accel kqemu,tcg', so I'm not sure
if this is desired to return (though I'm surely not comparing kvm to
kqemu here).
> - have distros / management tools decide which accel they like
That's likely the key: explicit -accel.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-07-29 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 20:52 [PATCH] exit if we fail to initialize kvm Glauber Costa
2009-07-28 21:12 ` Alexander Graf
2009-07-28 21:15 ` Alexander Graf
2009-07-28 21:28 ` Glauber Costa
2009-07-28 21:38 ` Alexander Graf
2009-07-28 22:12 ` Alexander Graf
2009-07-29 10:17 ` Jan Kiszka
2009-07-29 11:49 ` Avi Kivity
2009-07-29 12:28 ` Alexander Graf
2009-07-29 12:47 ` Avi Kivity
2009-07-29 14:43 ` Jan Kiszka [this message]
2009-07-29 15:50 ` Glauber Costa
2009-07-29 15:52 ` 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=4A705FFF.5060503@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.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