public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is it useful to support user level drivers
Date: Thu, 21 Jun 2001 18:06:39 -0400	[thread overview]
Message-ID: <200106212206.f5LM6dK12282@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.993156181.18994.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.993156181.18994.linux-kernel2news@redhat.com>

> There is no such thing as a "user mode" interrupt service routine.
> There never was one, and there will never be one on any machine
> that fetches instructions from memory for execution. [...]

If memory does not deceive me, SunLab Spring processed interrupts
in user space. I do not remember for sure, but I think QNX did, too.
User mode interrupt handlers are perfectly doable, provided that the
hardware allows to mask interrupts selectively.

Large part of the post that I quoted was spent on spitting
in the general direction of clueless programmers; indeed,
I observe that perhaps 90% of requests for user mode interrupt
processing come from the same people who would like to write
Linux kernel mode code in C++ (total retards, in other words).

It does not mean, however, that there are not justified cases
for user-mode interrupt handlers, especially outside of Linux.
Some OSes are even written in C++ and Java, and run just fine
on a machine that fetches instructions from memory.

-- Pete

       reply	other threads:[~2001-06-21 22:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.993156181.18994.linux-kernel2news@redhat.com>
2001-06-21 22:06 ` Pete Zaitcev [this message]
2001-06-21 22:20   ` Is it useful to support user level drivers David S. Miller
2001-06-21 23:09     ` Mike Mackovitch
2001-06-21 23:22       ` David S. Miller
2001-06-21 23:50         ` Mike Mackovitch
2001-06-22  0:36           ` David S. Miller
2001-06-21 23:40   ` Richard B. Johnson
2001-06-22  0:30     ` Anders Larsen
2001-06-22  0:43       ` Richard B. Johnson
2001-06-25  0:06         ` Anders Larsen
2001-06-21 10:41 Balbir Singh
2001-06-21 10:55 ` Tim Waugh
2001-06-21 11:04 ` Alan Cox
2001-06-21 12:43   ` Balbir Singh
2001-06-21 13:27     ` Alan Cox
2001-06-28 22:52     ` Pavel Machek
2001-06-21 12:45   ` Dmitry A. Fedorov
2001-06-21 13:24     ` Oliver Neukum
2001-06-21 14:46       ` Dmitry A. Fedorov
2001-06-21 15:19         ` Oliver Neukum
2001-06-22  4:19           ` Dmitry A. Fedorov
2001-06-22  7:28             ` Balbir Singh
2001-06-21 16:34         ` Abramo Bagnara
2001-06-21 17:27           ` Alan Cox
2001-06-21 19:59             ` Abramo Bagnara
2001-06-21 20:40               ` Richard B. Johnson
2001-06-21 20:54                 ` Abramo Bagnara
2001-06-21 21:09               ` Oliver Neukum
2001-06-28 22:57             ` Pavel Machek
2001-06-21 13:28     ` Alan Cox
2001-06-21 14:03       ` Matthias Urlichs
2001-06-28 22:54         ` Pavel Machek
2001-06-21 14:20       ` Dmitry A. Fedorov
2001-06-21 11:38 ` Dmitry A. Fedorov
2001-06-21 13:50   ` john slee
2001-06-21 13:58     ` Matthias Urlichs
2001-06-21 14:21       ` john slee
2001-06-28 22:51 ` Pavel Machek

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=200106212206.f5LM6dK12282@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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