public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: realtime-preempt patch-2.6.15-rt18 issues
Date: Mon, 6 Mar 2006 13:35:38 +0100	[thread overview]
Message-ID: <20060306123538.GA3844@elte.hu> (raw)
In-Reply-To: <45924.195.245.190.93.1141647094.squirrel@www.rncbc.org>


* Rui Nuno Capela <rncbc@rncbc.org> 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);
 }
 

  reply	other threads:[~2006-03-06 12:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06 12:11 realtime-preempt patch-2.6.15-rt18 issues Rui Nuno Capela
2006-03-06 12:35 ` Ingo Molnar [this message]
2006-03-06 13:24 ` Ingo Molnar
2006-03-06 15:10   ` Rui Nuno Capela
2006-03-07  9:40     ` [PATCH] realtime-preempt patch-2.6.15-rt19 compile error (was: realtime-preempt patch-2.6.15-rt18 issues) Jan Altenberg
2006-03-07 11:27       ` Ingo Molnar
2006-03-07 12:33       ` Rui Nuno Capela
2006-03-10  7:44         ` realtime-preempt patch-2.6.15-rt18 issues Jan Altenberg
2006-03-14 23:13         ` [PATCH] realtime-preempt patch-2.6.15-rt19 compile error (was: realtime-preempt patch-2.6.15-rt18 issues) karsten wiese
2006-03-15  9:31           ` Ingo Molnar
2006-03-15 10:19             ` Jan Altenberg
2006-03-15 11:04               ` Ingo Molnar
2006-03-15 14:08                 ` karsten wiese

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=20060306123538.GA3844@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rncbc@rncbc.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