From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60810) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WB43A-0006UV-62 for qemu-devel@nongnu.org; Wed, 05 Feb 2014 10:06:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WB434-0006K1-7G for qemu-devel@nongnu.org; Wed, 05 Feb 2014 10:06:04 -0500 Received: from cantor2.suse.de ([195.135.220.15]:36207 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WB434-0006Jx-15 for qemu-devel@nongnu.org; Wed, 05 Feb 2014 10:05:58 -0500 Message-ID: <52F25353.402@suse.de> Date: Wed, 05 Feb 2014 16:05:55 +0100 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <1391537199-13403-1-git-send-email-mst@redhat.com> In-Reply-To: <1391537199-13403-1-git-send-email-mst@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH] qtest: don't report signals if qtest driver enabled List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" , qemu-devel@nongnu.org Cc: Peter Maydell , Anthony Liguori Am 04.02.2014 19:06, schrieb Michael S. Tsirkin: > qtest driver always uses signals to kill qemu > no need to report it, whatever the accelerator state. >=20 > Add API to detect qtest driver, and suppress reporting > signals in this case. >=20 > Reported-by: Andreas F=E4rber > Signed-off-by: Michael S. Tsirkin Tested-by: Andreas F=E4rber We could do some bikeshedding about better names for qtest_driver(), but I'm happy to learn that it was just noise and not a real issue. I'll queue a copy for my qom-test work, but through whose queue should this best go? PMM directly? Thanks, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg