From: Paul Brook <paul@codesourcery.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Disabling kqemu by default at runtime for 0.11
Date: Thu, 9 Jul 2009 23:14:52 +0100 [thread overview]
Message-ID: <200907092314.52961.paul@codesourcery.com> (raw)
In-Reply-To: <4A565B42.3050005@us.ibm.com>
On Thursday 09 July 2009, Anthony Liguori wrote:
> We've talked about this at length but I'd like to pull the trigger. The
> user-visible change would be that -enable-kqemu would be required to
> explicitly request kqemu support instead of enabling it by default.
> kqemu would still be enabled by default at build time.
>
> Do you object to this Paul?
i have no objection to disabling kqemu by default *at runtime*. This would
make it the same as kvm.
On principle I object to having code that is disabled by default at configure
time. IMO that code should either be removed or fixed. If we were to disable
kqemu at configure time for 0.11 then I would expect to remove the code from
trunk shortly after 0.11 was released.
Paul
next prev parent reply other threads:[~2009-07-09 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 21:04 [Qemu-devel] Disabling kqemu by default at runtime for 0.11 Anthony Liguori
2009-07-09 22:14 ` Paul Brook [this message]
2009-07-09 22:29 ` [Qemu-devel] " Anthony Liguori
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=200907092314.52961.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aliguori@us.ibm.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).