All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Shepherd <mcs@astro.caltech.edu>
To: linux-rt-users@vger.kernel.org
Subject: Setting the priority of an IRQ thread
Date: Mon, 15 Jun 2009 22:44:39 +0000 (UTC)	[thread overview]
Message-ID: <loom.20090615T222836-377@post.gmane.org> (raw)

Is there a way for a device driver to set the priority of the IRQ thread that
services interrupts from its hardware? I am writing a device driver for a
digital I/O board with general purpose interrupt capability, and I would like
the application to be able to tell the driver what priority it needs those
interrupts to be given.

Currently it appears that preemp_rt spawns all IRQ threads with priority 50, and
that the only way to change the priority of an IRQ is for an application program
to execute the chrt program, after the IRQ thread has been created. However this
requires that the driver pass back information to the calling program about
which IRQ it is using, so that the program can then call popen to first search
for the PID of the corresponding thread, and then execute chrt to change its
priority. This is possible but messy, and relies on the name of IRQ threads not
changing in the future.

So is there a way for driver code in the kernel to identify the thread of a
given IRQ, and then change its priority?

Thanks,

Martin



             reply	other threads:[~2009-06-15 22:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-15 22:44 Martin Shepherd [this message]
2009-06-16  3:54 ` Setting the priority of an IRQ thread Suresh Kumar SHUKLA
2009-06-16  7:59   ` Martin Shepherd
2009-06-16 18:27     ` Uwe Kleine-König
2009-06-16 21:25       ` Martin Shepherd
2009-06-16 21:54       ` Martin Shepherd
2009-06-17  5:21         ` Thomas Gleixner
2009-06-17  6:09           ` Martin Shepherd
2009-06-17  9:00             ` Thomas Gleixner
2009-06-18  1:08               ` Martin Shepherd
2009-06-16 22:28       ` Thomas Gleixner
2009-06-17  1:12         ` GeunSik Lim
2009-06-17  2:27           ` Martin Shepherd
2009-06-17  5:28             ` Thomas Gleixner
2009-06-17  3:27         ` Martin Shepherd
2009-06-17  5:38           ` Thomas Gleixner
2009-06-17  9:17         ` Thomas Gleixner
2009-06-17 11:21           ` Remy Bohmer
2009-06-17 13:32             ` GeunSik Lim
2009-06-17 15:45               ` Thomas Gleixner
2009-06-17 13:54             ` Leon Woestenberg
2009-06-17 15:35             ` Thomas Gleixner
2009-06-17 20:14               ` Remy Bohmer
2009-06-17 23:32                 ` Thomas Gleixner
2009-06-18 11:05                 ` Suresh Kumar SHUKLA
2009-06-17  8:27     ` Thomas Pfaff
     [not found] <4A37E0CE020000D90003727B@sinclair.provo.novell.com>
2009-06-16 22:13 ` Peter Morreale

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=loom.20090615T222836-377@post.gmane.org \
    --to=mcs@astro.caltech.edu \
    --cc=linux-rt-users@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 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.