From: Greg KH <gregkh@suse.de>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 6/8] Kconfig: no userspace I/O on s390.
Date: Sun, 13 May 2007 02:35:58 -0700 [thread overview]
Message-ID: <20070513093558.GA11317@suse.de> (raw)
In-Reply-To: <1178181374.32267.17.camel@localhost>
On Thu, May 03, 2007 at 10:36:14AM +0200, Martin Schwidefsky wrote:
> On Wed, 2007-05-02 at 22:30 -0700, Greg KH wrote:
> > > Hide the config menu for userspace I/O on s390.
> >
> > Why? Who says s390 can't have userspace I/O drivers someday?
>
> Theoretically yes, but in practice this is very unlikely to happen. Some
> reasons why:
> 1) There are only very few device drivers for s390, the few we need
> we'll do as kernel space drivers
> 2) The irq abstraction of uio is awkward. The irq handler uses a 32-bit
> integer. On s390 each ccw device has it's own irq and ccw devices are
> identified with a string "x.y.zzzz". Then there are devices that deliver
> external interrupts where a 16-bit number is used to identify the
> source. You could invent some mapping logic of a 32 bit integer to all
> the possible interrupt sources but it doesn't really match.
> 3) s390 doesn't use memory mapped i/o, you always need to execute a
> privileged instruction to trigger activity on the device, e.g. ssch for
> a ccw device, siga for qdio, nqap for crypto, ...
>
> So I have my doubts that we will ever see a uio driver for s390. If we
> do we can unhide the config menu again.
Ok, that's find, can you bounce me the patch that made this change
again?
thanks,
greg k-h
prev parent reply other threads:[~2007-05-14 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 11:34 [PATCH 6/8] Kconfig: no userspace I/O on s390 Martin Schwidefsky
2007-05-03 5:30 ` Greg KH
2007-05-03 8:36 ` Martin Schwidefsky
2007-05-13 9:35 ` Greg KH [this message]
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=20070513093558.GA11317@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@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