From: Mark Hounschell <markh@compro.net>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Mai Daftedar <mai.daftedar@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Signal from kernel space to user space
Date: Tue, 01 Dec 2009 10:18:08 -0500 [thread overview]
Message-ID: <4B1533B0.1030007@compro.net> (raw)
In-Reply-To: <4B151A86.1060505@ladisch.de>
Clemens Ladisch wrote:
> Mai Daftedar wrote:
>> Im still new to the kernel development world :)and I was wondering
>> what functions I can use in the kernel space for a signal to be sent
>> to the userspace
>
I have some interest in this. Might I inject a couple of probably stupid related questions?
> kill_pid_(info) is to be preferred over send_sig_info because it ensures
> that the destination process has the same identity (a plain pid number
> might have wrappend around and be in use by another process).
>
Does that mean I can't assume my process pid will unique for the life of the process?
> However, why are you using a signal? What information are you trying to
> send, and why wouldn't eventfd or a plain device thaz becomes readable
> be a better solution?
>
If no "information" is required, which of these are the fastest, say from an interrupt handler?
I have a PCI card that handles external interrupts from the outside world and does nothing but
report those external interrupts to userland. We use send_sig or wake_up_process depending
on whether userland is going to wait for it or not. If there is a better/faster way I would be
very interested.
Thanks and sorry for butting in
Mark
next prev parent reply other threads:[~2009-12-01 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 11:07 Signal from kernel space to user space Mai Daftedar
2009-12-01 13:30 ` Clemens Ladisch
2009-12-01 15:18 ` Mark Hounschell [this message]
2009-12-01 18:05 ` Davide Libenzi
[not found] ` <2cd4ff050912020309j6e7c0ae9n89c011889b09f3e1@mail.gmail.com>
2009-12-02 11:26 ` Mai Daftedar
2009-12-02 12:28 ` Clemens Ladisch
2009-12-03 14:36 ` Eric W. Biederman
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=4B1533B0.1030007@compro.net \
--to=markh@compro.net \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mai.daftedar@gmail.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