From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:50669)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1QR35B-0005St-Us
	for qemu-devel@nongnu.org; Mon, 30 May 2011 10:04:38 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1QR35B-0007pC-40
	for qemu-devel@nongnu.org; Mon, 30 May 2011 10:04:37 -0400
Received: from goliath.siemens.de ([192.35.17.28]:18295)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1QR35A-0007ou-Qi
	for qemu-devel@nongnu.org; Mon, 30 May 2011 10:04:37 -0400
Message-ID: <4DE3A3EC.80201@siemens.com>
Date: Mon, 30 May 2011 16:04:28 +0200
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
References: <4DDAD5CF.5050805@redhat.com> <4DE0B4B1.1000407@web.de>
	<20110530081847.GC27062@amd.com>
In-Reply-To: <20110530081847.GC27062@amd.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [Qemu-devel] drop -enable-nesting (was: [PATCH 3/7] cpu model bug
 fixes and definition corrections...)
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

On 2011-05-30 10:18, Roedel, Joerg wrote:
> On Sat, May 28, 2011 at 04:39:13AM -0400, Jan Kiszka wrote:
>=20
>> J=F6rg, how to deal with -enable-nesting in qemu-kvm to align behavior
>> with upstream?
>=20
> 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

--=20
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux