* Rui Nuno Capela <[email protected]> wrote:
> Hi, Ingo,
>
> I think I would let you know that I'm still on 2.6.15-rt16, which
> works great for the most purposes, on all of my boxes.
>
> My problem is that the current/latest of the realtime-preempt patch,
> 2.6.15-rt18, has some showstoppers, at least for my day-to-day usage.
> The second issue seems to be related to the RTC and is not strictly
> specific to -rt18. AFAICT, my experience goes far as the ALSA MIDI
> sequencer is concerned (snd-seq-midi) and it badly shows whenever the
> RTC timer is used (snd-rtctimer), moreover if its used by default
> (i.e. CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y).
does the patch below (from Karsten Wiese) solve the second problem?
Ingo
-------
> the tasklet code was reworked too to be PREEMPT_RT friendly: the new
> PI code unearthed a fundamental livelock scenario with PREEMPT_RT, and
> the fix was to rework the tasklet code to get rid of the 'retrigger
> softirqs' approach.
following patch re enables tasklet_hi. needed by ALSA MIDI.
Karsten
--- linux/kernel/softirq.c.orig
+++ linux/kernel/softirq.c
@@ -351,13 +351,13 @@
static DEFINE_PER_CPU(struct tasklet_head, tasklet_hi_vec) = { NULL };
static void inline
-__tasklet_common_schedule(struct tasklet_struct *t, struct tasklet_head *head)
+__tasklet_common_schedule(struct tasklet_struct *t, struct tasklet_head *head, unsigned int nr)
{
if (tasklet_trylock(t)) {
WARN_ON(t->next != NULL);
t->next = head->list;
head->list = t;
- raise_softirq_irqoff(TASKLET_SOFTIRQ);
+ raise_softirq_irqoff(nr);
tasklet_unlock(t);
}
}
@@ -367,7 +367,7 @@
unsigned long flags;
raw_local_irq_save(flags);
- __tasklet_common_schedule(t, &__get_cpu_var(tasklet_vec));
+ __tasklet_common_schedule(t, &__get_cpu_var(tasklet_vec), TASKLET_SOFTIRQ);
raw_local_irq_restore(flags);
}
@@ -378,7 +378,7 @@
unsigned long flags;
raw_local_irq_save(flags);
- __tasklet_common_schedule(t, &__get_cpu_var(tasklet_hi_vec));
+ __tasklet_common_schedule(t, &__get_cpu_var(tasklet_hi_vec), HI_SOFTIRQ);
raw_local_irq_restore(flags);
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
