mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: daniel sheltraw <l5gibson@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel to user-space communication
Date: Mon, 12 Aug 2002 17:51:30 +0200	[thread overview]
Message-ID: <20020812155130.GE14305@vagabond> (raw)
In-Reply-To: <F137zkftciAlUNLFAYp000015b2@hotmail.com>

On Mon, Aug 12, 2002 at 10:40:27AM -0500, daniel sheltraw wrote:
> Is there a way to comminicate to a user-space program that an
> interrupt has occurred in a kernel module?

You can send a signal or you can create a device for a process to wait
on in poll or blocking read. Signals have quite high overhead because of
the need to save state, so device will be faster (it's faster even if
the process shoul clone a thread to handle it).

-------------------------------------------------------------------------------
						 Jan 'Bulb' Hudec <bulb@ucw.cz>

  reply	other threads:[~2002-08-12 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-12 15:40 daniel sheltraw
2002-08-12 15:51 ` Jan Hudec [this message]
2002-08-12 16:04 ` Richard B. Johnson
2002-08-12 17:52 Woodruff, Robert J
2002-08-13  7:24 ` Jan Hudec

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=20020812155130.GE14305@vagabond \
    --to=bulb@ucw.cz \
    --cc=l5gibson@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®