From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56035) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VWlPE-000300-Ck for qemu-devel@nongnu.org; Thu, 17 Oct 2013 07:06:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VWlP7-0004GZ-HA for qemu-devel@nongnu.org; Thu, 17 Oct 2013 07:06:16 -0400 Received: from mx1.redhat.com ([209.132.183.28]:62374) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VWlP7-0004GF-7V for qemu-devel@nongnu.org; Thu, 17 Oct 2013 07:06:09 -0400 Message-ID: <525FC499.3070809@redhat.com> Date: Thu, 17 Oct 2013 13:06:01 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <525D5630.1030801@redhat.com> <87txgimrd6.fsf@codemonkey.ws> <20131015201706.GB9579@redhat.com> <20131016181800.GB7100@redhat.com> <20131016183732.GA8157@redhat.com> <525F0473.6060408@redhat.com> <20131016220301.GA10908@redhat.com> <525F125C.80403@redhat.com> <20131017053442.GD12141@redhat.com> In-Reply-To: <20131017053442.GD12141@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PULL 42/43] piix4: add acpi pci hotplug support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: Peter Maydell , gleb@redhat.com, marcel.a@redhat.com, qemu-devel , Gerd Hoffmann , Anthony Liguori , Igor Mammedov Il 17/10/2013 07:34, Michael S. Tsirkin ha scritto: > > So we could have a qtest for sanity checking ACPI tables. At least > > fw_cfg is one of the few components that has qtest infrastructure... I > > don't think we need to do more than that though. The set of sanity > > checks can start with a simple list of tables that "have to be there" > > for a given machine type. > > Well this means these tests won't pass on old qemu so > they would be useless for comparing old to new. Yes, they would be correctness tests not compatibility tests. > And in this case, while it's a good idea to have them > I don't see why it's a blocker for merging. In principle, correctness tests should be a prerequisite for merging something. Would you merge RCU without an equivalent of rcutorture? We rarely if ever obey that principle, but we sometimes do (e.g. QAPI has pretty good test cases, and new additions to util/ almost always get new testcases these days). Paolo