mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mai Daftedar <mai.daftedar@gmail.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Mark Hounschell <markh@compro.net>,
	Clemens Ladisch <clemens@ladisch.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Signal from kernel space to user space
Date: Wed, 2 Dec 2009 13:26:24 +0200	[thread overview]
Message-ID: <2cd4ff050912020326rcd2d7ffseb481ca736cd7d8c@mail.gmail.com> (raw)
In-Reply-To: <2cd4ff050912020309j6e7c0ae9n89c011889b09f3e1@mail.gmail.com>

Thanks all for the help,
 I needed to use signals just as interrupt signal from the kernel
space so that when a certain change occurs I'd be notified in the
userspace
 I used send_sig _info and it worked :)..The problem was with the
signal number I using a wong one..

 Thanks


> On Tue, Dec 1, 2009 at 8:05 PM, Davide Libenzi <davidel@xmailserver.org> wrote:
>>
>> On Tue, 1 Dec 2009, Mark Hounschell wrote:
>>
>> > 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.
>>
>> eventfd is. eventfd_signal() is also callable from non-sleeping contexts.
>>
>>
>> - Davide
>>
>>
>

  parent reply	other threads:[~2009-12-02 11:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 11:07 Mai Daftedar
2009-12-01 13:30 ` Clemens Ladisch
2009-12-01 15:18   ` Mark Hounschell
2009-12-01 18:05     ` Davide Libenzi
     [not found]       ` <2cd4ff050912020309j6e7c0ae9n89c011889b09f3e1@mail.gmail.com>
2009-12-02 11:26         ` Mai Daftedar [this message]
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=2cd4ff050912020326rcd2d7ffseb481ca736cd7d8c@mail.gmail.com \
    --to=mai.daftedar@gmail.com \
    --cc=clemens@ladisch.de \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    /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