From: Monica Puig-Pey <puigpeym@unican.es>
To: <linux-kernel@vger.kernel.org>
Subject: How to establish a priority to an interrupt handler
Date: Tue, 17 May 2011 13:51:38 +0200 [thread overview]
Message-ID: <4DD2614A.4060003@unican.es> (raw)
Hi,
I'm using Ubuntu 10.04 with the 2.6.31-11-rt patch installed. I'm
developing a PCI device driver using hardware interrupts.
As I read at the RT wiki
(https://rt.wiki.kernel.org/index.php/CONFIG_PREEMPT_RT_Patch )
interrupts are moved to kernel threads called Threaded Interrupts in the
RT patch.
I would like to give a priority chosen by me to my IRQ handler, but I
don't know how to do it, or if it is possible (it seems it is).
I've found (http://lwn.net/Articles/302043/ ) that what I had to use in
order to get Threaded Interrupt is:
int request_threaded_irq(unsigned int irq, irq_handler_t handler,
irq_handler_t quick_check_handler,
unsigned long flags, const char *name, void *dev)
But there is not priority there!
Using ps -eo pid,pri,rtprio,cmd I've seen my handler runs with priority 50.
I also used :
int request_irq (unsigned int irq, void (*handler) (int, void *, struct
pt_regs *), unsigned long irqflags, const char *devname, void *dev_id);
and using ps command here my handler still runs with priority 50.
Shouldn't it work as a non threaded interrupt then? Why 50 instead 99 or
the highest priority one?
Which function should I use to chose the priority for the IRQ thread?
Is there any other function to call from this context where my handler
could know its priority?
Please I wish to be personally CC'ed the answers/comments posted to the
list in response to my posting because I'm not subscribed to the list.
Thank you very much
Mónica
next reply other threads:[~2011-05-17 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 11:51 Monica Puig-Pey [this message]
2011-05-18 8:01 ` Clemens Ladisch
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=4DD2614A.4060003@unican.es \
--to=puigpeym@unican.es \
--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
Powered by JetHome