mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Steven J. Magnani" <steve@digidescorp.com>
To: andi@firstfloor.org, LKML <linux-kernel@vger.kernel.org>
Cc: rjw@sisk.pl, stable@kernel.org, a.p.zijlstra@chello.nl
Subject: Re: [Bug #23902] 2.6.37-rc3 massive interactivity regression on ARM
Date: Wed, 25 May 2011 09:56:51 -0500	[thread overview]
Message-ID: <1306335411.2643.21.camel@iscandar.digidescorp.com> (raw)

Andi -

This bug appears to have crept into 2.6.35.12 via
a3fe22ee824895aafdc1b788e19c081a2e6dd9da and is still present in
2.6.35.13.

Mainline patch fe44d62122829959e960bc699318d58966922a69 (sched: Fix the
irqtime code to deal with u64 wraps) seems to fix my system although I
recommend also applying  8e92c20183ed0579d94501311b81c42b65cb2129
(sched: Fix the irqtime code for 32bit). Any stable releases that have
picked up 305e6835e05513406fa12820e40e4a8ecb63743c (sched: Do not
account irq time to current task) should probably also apply these.

Before I could get these patches to apply to 2.6.35.13 I had to tweak
sched.c:update_rq_clock() to match
f26f9aff6aaf67e9a430d16c266f91b13a5bff64 (Sched: fix skip_clock_update
optimization). That patch was applied to 2.6.35-longterm, except for the
update_rq_clock() portion. I believe that was because that portion
depended on a patch from Ventakesh that wasn't applied until later. It
looks like the logic that ended up in 2.6.35.12 was slightly different
than in mainline; I'm not familiar enough with the scheduler details to
know what the effects would be.

------------------------------------------------------------------------
Signed-off-by: Steven J. Magnani <steve@digidescorp.com>
---
diff -uprN a/kernel/sched.c b/kernel/sched.c
--- a/kernel/sched.c	2011-05-25 09:39:05.200320708 -0500
+++ b/kernel/sched.c	2011-05-25 09:39:27.990238065 -0500
@@ -654,8 +654,10 @@ inline void update_rq_clock(struct rq *r
 	int cpu = cpu_of(rq);
 	u64 irq_time;
 
-	if (!rq->skip_clock_update)
-		rq->clock = sched_clock_cpu(cpu_of(rq));
+	if (rq->skip_clock_update)
+		return;
+
+	rq->clock = sched_clock_cpu(cpu);
 	irq_time = irq_time_cpu(cpu);
 	if (rq->clock - irq_time > rq->clock_task)
 		rq->clock_task = rq->clock - irq_time;
------------------------------------------------------------------------
 Steven J. Magnani               "I claim this network for MARS!
 www.digidescorp.com              Earthling, return my space modulator!"

 #include <standard.disclaimer>




                 reply	other threads:[~2011-05-25 15:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1306335411.2643.21.camel@iscandar.digidescorp.com \
    --to=steve@digidescorp.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=stable@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

all inboxes | Powered by JetHome®