From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50045) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dspT7-0002kK-Ms for qemu-devel@nongnu.org; Fri, 15 Sep 2017 08:11:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dspT6-0008VD-Qj for qemu-devel@nongnu.org; Fri, 15 Sep 2017 08:11:37 -0400 Date: Fri, 15 Sep 2017 14:11:19 +0200 From: Kevin Wolf Message-ID: <20170915121119.GB4077@localhost.localdomain> References: <20170913091038.2900-1-cohuck@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170913091038.2900-1-cohuck@redhat.com> Subject: Re: [Qemu-devel] [PATCH v2 0/3] iotests: cure s390x failures by switching to ccw/aliases List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cornelia Huck Cc: mreitz@redhat.com, qemu-block@nongnu.org, qemu-devel@nongnu.org, borntraeger@de.ibm.com, agraf@suse.de, thuth@redhat.com, david@redhat.com, haoqf@linux.vnet.ibm.com Am 13.09.2017 um 11:10 hat Cornelia Huck geschrieben: > Recent changes in s390x made pci support dependant on the zpci cpu > feature, which is not provided on all models (and not on by default). > This means we cannot instatiate pci devices on a standard qemu > invocation for s390x. Moreover, the zpci instructions are not even > wired up for tcg yet, so actually doing anything with those pci devices > is bound to fail on tcg. > > For 040, 051, 139, and 182, this can be fixed by switching to virtio-ccw > from virtio-pci on s390x. 051 also needs a bit of post-processing on > the output. > > For 067, it is easier to switch to virtio aliases, which will pick > virtio-ccw on s390x and virtio-pci elsewhere. It also exercises the > aliasing path. Thanks, dropped the whitespace change in patch 3 and applied to the block branch. Kevin