LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
	LKML <linux-kernel@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.24-rc7-rt1
Date: Mon, 14 Jan 2008 09:27:40 +0100	[thread overview]
Message-ID: <1200299260.4665.17.camel@homer.simson.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0801131552350.10093@gandalf.stny.rr.com>


On Sun, 2008-01-13 at 15:54 -0500, Steven Rostedt wrote:

> OK, -rt2 will take a bit more beating from me before I release it, so it
> might take some time to get it out (expect it out on Monday).

Ah, that reminds me (tests, yup) I still need the patchlet below to
resume from ram without black screen of death.  No idea why my P4 box
seems to be the only box in the rt galaxy affected.  (haven't poked at
it since the holidays)

Index: linux-2.6.24.git-rt1/kernel/sched_rt.c
===================================================================
--- linux-2.6.24.git-rt1.orig/kernel/sched_rt.c
+++ linux-2.6.24.git-rt1/kernel/sched_rt.c
@@ -33,6 +33,9 @@ static inline void rt_clear_overload(str
 
 static void update_rt_migration(struct rq *rq)
 {
+	if (unlikely(num_online_cpus() == 1))
+		return;
+
 	if (rq->rt.rt_nr_migratory && (rq->rt.rt_nr_running > 1)) {
 		if (!rq->rt.overloaded) {
 			rt_set_overload(rq);
@@ -105,8 +108,10 @@ static inline void dec_rt_tasks(struct t
 		} /* otherwise leave rq->highest prio alone */
 	} else
 		rq->rt.highest_prio = MAX_RT_PRIO;
-	if (p->nr_cpus_allowed > 1)
+	if (p->nr_cpus_allowed > 1) {
+		BUG_ON(!rq->rt.rt_nr_migratory);
 		rq->rt.rt_nr_migratory--;
+	}
 
 	if (rq->rt.highest_prio != highest_prio)
 		cpupri_set(&rq->rd->cpupri, rq->cpu, rq->rt.highest_prio);


btw, CONFIG_INTEL_IOATDMA compile booboo

  CC      drivers/dma/ioat_dma.o
drivers/dma/ioat_dma.c: In function ‘ioat1_tx_submit’:
drivers/dma/ioat_dma.c:300: error: too few arguments to function ‘__list_splice’
make[2]: *** [drivers/dma/ioat_dma.o] Error 1



  reply	other threads:[~2008-01-14  8:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 19:00 2.6.24-rc7-rt1 Steven Rostedt
2008-01-13 19:53 ` 2.6.24-rc7-rt1: macro "put_cpu_var" passed 2 arguments, but takes just 1 Mariusz Kozlowski
2008-01-13 20:37   ` Steven Rostedt
2008-01-13 20:25 ` 2.6.24-rc7-rt1 Robert Schwebel
2008-01-13 20:48   ` 2.6.24-rc7-rt1 Steven Rostedt
2008-01-14 19:49     ` 2.6.24-rc7-rt1 Robert Schwebel
2008-01-13 20:43 ` 2.6.24-rc7-rt1 Mariusz Kozlowski
2008-01-13 20:54   ` 2.6.24-rc7-rt1 Steven Rostedt
2008-01-14  8:27     ` Mike Galbraith [this message]
2008-01-14 12:13       ` 2.6.24-rc7-rt1 Gregory Haskins
2008-01-14 13:25         ` 2.6.24-rc7-rt1 Mike Galbraith
2008-01-14 14:29           ` 2.6.24-rc7-rt1 Mike Galbraith
2008-01-15  8:07           ` 2.6.24-rc7-rt1 Mike Galbraith
2008-01-15  9:28             ` 2.6.24-rc7-rt1 Mike Galbraith
2008-01-15 16:50               ` 2.6.24-rc7-rt1 Gregory Haskins
2008-01-14 18:39       ` 2.6.24-rc7-rt1 S.Çağlar Onur
2008-01-14 16:52         ` 2.6.24-rc7-rt1 Steven Rostedt
2008-01-13 22:56 ` 2.6.24-rc7-rt1 Mark Knecht

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=1200299260.4665.17.camel@homer.simson.net \
    --to=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=m.kozlowski@tuxland.pl \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).