From: Till Straumann <strauman@slac.stanford.edu>
To: Tim Sander <tim01@vlsi.informatik.tu-darmstadt.de>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: How to unblock a thread from a hard isr (IRQF_NO_THREAD)
Date: Thu, 08 Nov 2012 18:53:35 -0600 [thread overview]
Message-ID: <509C540F.3050108@slac.stanford.edu> (raw)
In-Reply-To: <201211090012.32207.tim01@vlsi.informatik.tu-darmstadt.de>
On 11/08/2012 05:12 PM, Tim Sander wrote:
> Hi Till
>> What *is* the recommended mechanism to wake up a thread from
>> a hard-isr?
> I think its the waitqueue mechanism with the drawbacks you mentioned.
I thought I can't wake_up() from a hard-isr so that can hardly be
the recommended mechanism (unless you mean I *should* go
via the 'irq_thread' (kernel/irq/management.c) and wake my
user-land thread from there).
The IRQ management code must use something to let the
hard-isr unblock the irq-handler kthread - I'd like to use the same
(or a similar) method to let the hard-isr unblock a user-land
thread.
>
> If you only want to wake up *one* usermode thread there is a hack
> possible to save the context switch times to the bottom half interrupt thread?
What would such a hack be?
Thanks
- Till
>
> Best regards
> Tim
next prev parent reply other threads:[~2012-11-09 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 22:28 How to unblock a thread from a hard isr (IRQF_NO_THREAD) Till Straumann
2012-11-08 23:12 ` Tim Sander
2012-11-09 0:53 ` Till Straumann [this message]
[not found] ` <201211091518.36344.tim01@vlsi.informatik.tu-darmstadt.de>
2012-11-09 17:27 ` Till Straumann
2012-11-09 4:08 ` Josh Cartwright
2012-11-09 4:28 ` Till Straumann
2012-11-09 4:42 ` Josh Cartwright
2012-11-09 4:50 ` Till Straumann
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=509C540F.3050108@slac.stanford.edu \
--to=strauman@slac.stanford.edu \
--cc=linux-rt-users@vger.kernel.org \
--cc=tim01@vlsi.informatik.tu-darmstadt.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.