mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Smith <gsmith@nc.rr.com>
To: linux-kernel@vger.kernel.org
Cc: schwidefsky@de.ibm.com, cornelia.huck@de.ibm.com
Subject: Re: [patch 16/17] s390: multiple subchannel sets support.
Date: Sat, 25 Feb 2006 06:12:02 -0500	[thread overview]
Message-ID: <1140865922.3513.87.camel@localhost.localdomain> (raw)

Running linux-2.6.16-rc4 on the hercules s390x emulator we noticed a
boatload of program checks on the stsch instruction, 192K to be exact.
Hercules does not support multiple subchannel sets at this time.
However, __init_channel_subsystem does not recognize the -EIO return
code from css_alloc_subchannel.

Further investigation shows that this would have been avoided if the
response code from the chsc instruction was properly handled.  In this
case chsc_enable_facility should have returned -EINVAL causing
init_channel_subsystem to set max_ssid to zero.  But the response code
0x0002 (invalid request) is not checked and chsc_enable_facility returns
0 causing max_ssid to be set to __MAX_SSID.

I have verified that on a real machine that does not support multiple
channel sets (a 9672) the CHSC_SDA_OC_MSS chsc request gets response
code 0x0002.  The emulator also sets the response code to 0x0002.

Users of the emulator can do `pgmtrace -15' to supress the 3.7 million
or so lines it spits out ;-)

Greg Smith

--- linux-2.6.16-rc4/drivers/s390/cio/css.c.orig	2006-02-23 17:59:08.000000000 -0500
+++ linux-2.6.16-rc4/drivers/s390/cio/css.c	2006-02-24 12:44:09.000000000 -0500
@@ -409,6 +409,9 @@
 		/* -ENXIO: no more subchannels. */
 		case -ENXIO:
 			return ret;
+		/* -EIO: this subchannel set not supported. */
+		case -EIO:
+			return ret;
 		default:
 			return 0;
 		}


--- linux-2.6.16-rc4/drivers/s390/cio/chsc.c.orig	2006-02-23 17:59:08.000000000 -0500
+++ linux-2.6.16-rc4/drivers/s390/cio/chsc.c	2006-02-25 05:43:24.000000000 -0500
@@ -1115,6 +1115,7 @@
 		goto out;
 	}
 	switch (sda_area->response.code) {
+	case 0x0002: /* invalid request */
 	case 0x0003: /* invalid request block */
 	case 0x0007:
 		ret = -EINVAL;



             reply	other threads:[~2006-02-25 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25 11:12 Greg Smith [this message]
2006-02-27  8:15 ` Cornelia Huck
2006-02-27 22:02   ` Greg Smith
2006-03-13 22:18   ` Greg Smith
2006-03-14  8:29     ` Cornelia Huck
  -- strict thread matches above, loose matches on Subject: below --
2005-12-09 15:29 Martin Schwidefsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1140865922.3513.87.camel@localhost.localdomain \
    --to=gsmith@nc.rr.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome