From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37153) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XH1RU-0002zq-Sq for qemu-devel@nongnu.org; Mon, 11 Aug 2014 22:04:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XH1RO-0000Im-LQ for qemu-devel@nongnu.org; Mon, 11 Aug 2014 22:04:04 -0400 Received: from mx1.redhat.com ([209.132.183.28]:9710) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XH1RO-0000If-DN for qemu-devel@nongnu.org; Mon, 11 Aug 2014 22:03:58 -0400 Date: Tue, 12 Aug 2014 10:04:11 +0800 From: Fam Zheng Message-ID: <20140812020411.GD6226@T430.nay.redhat.com> References: <1407746718-16527-1-git-send-email-famz@redhat.com> <1407746718-16527-3-git-send-email-famz@redhat.com> <20140811143214.GC496@stefanha-thinkpad.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140811143214.GC496@stefanha-thinkpad.redhat.com> Subject: Re: [Qemu-devel] [PATCH v3 2/2] scsi-bus: Convert DeviceClass init to realize List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: kwolf@redhat.com, pbonzini@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com, armbru@redhat.com On Mon, 08/11 15:32, Stefan Hajnoczi wrote: > On Mon, Aug 11, 2014 at 04:45:18PM +0800, Fam Zheng wrote: > > diff --git a/tests/qemu-iotests/051.out b/tests/qemu-iotests/051.out > > index d7b0f50..f6d9dc1 100644 > > --- a/tests/qemu-iotests/051.out > > +++ b/tests/qemu-iotests/051.out > > @@ -122,7 +122,7 @@ QEMU_PROG: -drive if=virtio: Device 'virtio-blk-pci' could not be initialized > > > > Testing: -drive if=scsi > > QEMU X.Y.Z monitor - type 'help' for more information > > -(qemu) QEMU_PROG: -drive if=scsi: Device needs media, but drive is empty > > +(qemu) QEMU_PROG: Device needs media, but drive is empty > > QEMU_PROG: Device initialization failed. > > QEMU_PROG: Initialization of device lsi53c895a failed > > > > Have you checked where error_report()'s "location" was set to "-drive > if=scsi"? > > Maybe something similar can be implemented. Yes. In scsi_bus_legacy_handle_cmdline (callee of lsi, location is maintained until function return. Since its callers only use "err" for failure detection, but not for reporting (the specific information) to user, let's call error_report in scsi_bus_legacy_handle_cmdline. Thanks, Fam