From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49303) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fbLGs-0008Oo-JT for qemu-devel@nongnu.org; Fri, 06 Jul 2018 03:35:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fbLGq-00008k-8K for qemu-devel@nongnu.org; Fri, 06 Jul 2018 03:35:14 -0400 Date: Fri, 6 Jul 2018 09:35:08 +0200 From: Cornelia Huck Message-ID: <20180706093508.0c4bf0cf.cohuck@redhat.com> In-Reply-To: <1530811543-6881-3-git-send-email-jjherne@linux.ibm.com> References: <1530811543-6881-1-git-send-email-jjherne@linux.ibm.com> <1530811543-6881-3-git-send-email-jjherne@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC 02/15] s390-bios: decouple cio setup from virtio List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Jason J. Herne" Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org, pasic@linux.ibm.com, bjsdjshi@linux.ibm.com, borntraeger@de.ibm.com On Thu, 5 Jul 2018 13:25:30 -0400 "Jason J. Herne" wrote: > From: "Jason J. Herne" > > Move channel i/o setup code out to a separate function. This decouples cio > setup from the virtio code path and allows us to make use of it for booting > dasd devices. > > Signed-off-by: Jason J. Herne > Acked-by: Halil Pasic > Reviewed-by: Collin Walling > Signed-off-by: Jason J. Herne > --- > pc-bios/s390-ccw/main.c | 20 +++++++++++++------- > 1 file changed, 13 insertions(+), 7 deletions(-) > > diff --git a/pc-bios/s390-ccw/main.c b/pc-bios/s390-ccw/main.c > index 544851d..63117d1 100644 > --- a/pc-bios/s390-ccw/main.c > +++ b/pc-bios/s390-ccw/main.c > @@ -99,6 +99,18 @@ static void menu_setup(void) > } > } > > +/* > + * Initialize the channel I/O subsystem so we can talk to our ipl/boot device. > + */ > +static void cio_setup(void) Call this css_setup? > +{ > + /* > + * Unconditionally enable mss support. In every sane configuration this > + * will succeed; and even if it doesn't, stsch_err() can handle it. > + */ > + enable_mss_facility(); > +} > + > static void virtio_setup(void) > { > Schib schib;