From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: john cooper <john.cooper@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] drop -enable-nesting (was: [PATCH 3/7] cpu model bug fixes and definition corrections...)
Date: Mon, 30 May 2011 16:04:28 +0200 [thread overview]
Message-ID: <4DE3A3EC.80201@siemens.com> (raw)
In-Reply-To: <20110530081847.GC27062@amd.com>
On 2011-05-30 10:18, Roedel, Joerg wrote:
> On Sat, May 28, 2011 at 04:39:13AM -0400, Jan Kiszka wrote:
>
>> Jörg, how to deal with -enable-nesting in qemu-kvm to align behavior
>> with upstream?
>
> My personal preference is to just remove it. In upstream-qemu it is
> enabled/disabled by +/-svm. -enable-nesting is just a historic thing
> which can be wiped out.
Does any user land depend on it? I guess we have to flag it deprecated
first, trigger some console output when it's specified, and then remove
it one or more releases later (the same applies to many other
qemu-kvm-specific switches).
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-05-30 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 21:46 [Qemu-devel] [PATCH 3/7] cpu model bug fixes and definition corrections: Add kvm emulated x2apic flag to config defined cpu models john cooper
2011-05-28 8:39 ` Jan Kiszka
2011-05-30 8:18 ` Roedel, Joerg
2011-05-30 14:04 ` Jan Kiszka [this message]
2011-05-30 14:38 ` [Qemu-devel] drop -enable-nesting (was: [PATCH 3/7] cpu model bug fixes and definition corrections...) Nadav Har'El
2011-05-30 15:04 ` [Qemu-devel] drop -enable-nesting Jan Kiszka
2011-05-30 15:10 ` Roedel, Joerg
2011-05-30 15:15 ` Jan Kiszka
2011-05-30 15:19 ` Avi Kivity
2011-05-30 15:27 ` Jan Kiszka
2011-05-30 15:42 ` Jan Kiszka
2011-05-31 8:44 ` Daniel P. Berrange
2011-05-31 8:58 ` Avi Kivity
2011-05-31 9:06 ` Roedel, Joerg
2011-05-31 9:15 ` Paolo Bonzini
2011-05-31 9:16 ` Avi Kivity
2011-05-30 15:16 ` Nadav Har'El
2011-05-30 15:59 ` Jan Kiszka
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=4DE3A3EC.80201@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Joerg.Roedel@amd.com \
--cc=aliguori@us.ibm.com \
--cc=john.cooper@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 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).