public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrik Austad <henrik@austad.us>
To: Chris Caudle <chris@chriscaudle.org>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: replacement of tasklet_hrtimer_init in RT
Date: Wed, 25 Oct 2017 07:34:41 +0200	[thread overview]
Message-ID: <20171025053441.GA2280@sisyphus.home.austad.us> (raw)
In-Reply-To: <69d8d76f1173a449bce4a3bc3a9e1a06.squirrel@email.powweb.com>

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

Hi Chris,

On Tue, Oct 24, 2017 at 11:33:46AM -0500, Chris Caudle wrote:
> I recently began helping someone test a new multimedia driver (network
> audio) and found that the driver would not compile on my machine running
> an RT kernel because the driver used tasklet_hrtimer_init(), but that
> function is not defined in interrupt.h in the RT  patched kernel.

/me eyes include/linux/interupt.h and kernel/softirq.c and finds 
tasklet_hrtimer_init().

It is marked EXPORT_SYMBOL_GPL() though, so if you do not export the 
modules as GPL, it won't resolve that symbol.

If this is not the case, please provide which kernel-version and PREEMPT-RT 
patch version you are using. A .config would probably also be helpful.

> What should be used in place of that, and where should be look for
> documentation describing any differences that need to be accomodated?

Using tasklets is somewhat frowned upon -have you tried using a 
kernelthread instead? (You can adjust priority and set affinity for 
threads)

-Henrik

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-10-25  5:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 16:33 replacement of tasklet_hrtimer_init in RT Chris Caudle
2017-10-25  5:34 ` Henrik Austad [this message]
2017-10-25 16:50   ` Chris Caudle
2017-10-25 19:40     ` Chris Caudle
2017-10-25 20:48     ` Henrik Austad
2017-10-26 15:40 ` Sebastian Andrzej Siewior

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=20171025053441.GA2280@sisyphus.home.austad.us \
    --to=henrik@austad.us \
    --cc=chris@chriscaudle.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox