From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46673) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsB19-00052B-Dv for qemu-devel@nongnu.org; Thu, 06 Oct 2016 11:55:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bsB18-0008C7-HK for qemu-devel@nongnu.org; Thu, 06 Oct 2016 11:55:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52754) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsB18-0008Bk-6V for qemu-devel@nongnu.org; Thu, 06 Oct 2016 11:55:30 -0400 Date: Thu, 6 Oct 2016 17:55:25 +0200 From: Radim =?utf-8?B?S3LEjW3DocWZ?= Message-ID: <20161006155525.GB19924@potion> References: <20161005130657.3399-1-rkrcmar@redhat.com> <20161005130657.3399-8-rkrcmar@redhat.com> <20161006145142.GR3877@thinpad.lan.raisama.net> <20161006183130-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20161006183130-mutt-send-email-mst@kernel.org> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v4 7/8] intel_iommu: keep buggy EIM enabled in 2.7 machine type List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Eduardo Habkost , qemu-devel@nongnu.org, Peter Xu , Igor Mammedov , Paolo Bonzini , Richard Henderson 2016-10-06 18:33+0300, Michael S. Tsirkin: > On Thu, Oct 06, 2016 at 11:51:42AM -0300, Eduardo Habkost wrote: >> On Wed, Oct 05, 2016 at 03:06:56PM +0200, Radim Kr=C4=8Dm=C3=A1=C5=99 = wrote: >> > QEMU 2.7 allowed EIM even in configurations that were forbidden in t= he >> > last patch because they were not working, like old KVM or userspace >> > APIC. In order to keep backward compatibility, we again allow guest= s to >> > misbehave in non-obvious ways, and make it the default for old machi= ne >> > types. >> >=20 >> > A user can enable the buggy mode it with "buggy_eim=3Don", which is = weird, >> > but I don't know how to add a private property. >>=20 >> Properties et by compat_props are always user-visible. I believe >> that's a feature (this way, it will be possible to let management >> software and other tools know what exactly is behind a >> machine-type). >=20 > There's a rule that any name beginning with x- is deemed > experimental. See docs/qmp-spec.txt. > It is a good idea to always use this for compat properties as > we want to be able to drop them when we drop the old > machine type. "x-buggy-eim" should deter most users, thanks. pc-0.10 seems to be the first machine type ever (2009), is there already a plan to deprecate it?