All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Lukas Hejtmanek <xhejtman@ics.muni.cz>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Marcin Slusarz <marcin.slusarz@gmail.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Bootup time regression from 2.6.27 to 2.6.28-rc3+
Date: Sun, 9 Nov 2008 12:48:36 -0800	[thread overview]
Message-ID: <20081109124836.34a2c126@infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0811091237110.3468@nehalem.linux-foundation.org>

On Sun, 9 Nov 2008 12:39:50 -0800 (PST)
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> 
> 
> On Sun, 9 Nov 2008, Arjan van de Ven wrote:
> > 
> > for me, the plan is that we need to get Thomas' fixes tested by
> > someone who can reproduce this very reliably. If they fix it, great.
> > If they don't, time is running out and we need to remove the feature
> > for 2.6.28 (that is 1 line of change), realizing that this just
> > papers over stuff and isn't a real fix, and get back to it for
> > 2.6.29.
> 
> I'd like to see the one-liner fix, even if it turns out to just be a 
> workaround that hides the issue and makes us go back to 2.6.27
> behaviour. I'm about to release -rc4 today, we should be aggressive
> about regressions.

>From bf1003799b70f68f927d312841a05930856ad716 Mon Sep 17 00:00:00 2001
From: Arjan van de Ven <arjan@linux.intel.com>
Date: Sun, 9 Nov 2008 12:45:10 -0800
Subject: [PATCH] regression: disable timer peek-ahead for 2.6.28

it's showing up as regressions; disabling it very likely just papers
over an underlying issue, but time is running out for 2.6.28,
lets get back to this for 2.6.29

Fixes: #11826 and #11893

Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
---
 drivers/cpuidle/cpuidle.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c
index 5bed733..67ec4da 100644
--- a/drivers/cpuidle/cpuidle.c
+++ b/drivers/cpuidle/cpuidle.c
@@ -65,12 +65,14 @@ static void cpuidle_idle_call(void)
 		return;
 	}
 
+#if 0
+	/* shows regressions, re-enable for 2.6.29 */
 	/*
 	 * run any timers that can be run now, at this point
 	 * before calculating the idle duration etc.
 	 */
 	hrtimer_peek_ahead_timers();
-
+#endif
 	/* ask the governor for the next state */
 	next_state = cpuidle_curr_governor->select(dev);
 	if (need_resched())
-- 
1.6.0.3


  reply	other threads:[~2008-11-09 20:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-04 17:33 Bootup time regression from 2.6.27 to 2.6.28-rc3+ Lukas Hejtmanek
2008-11-09  0:06 ` Rafael J. Wysocki
2008-11-09  4:55   ` Arjan van de Ven
2008-11-09  8:56     ` Lukas Hejtmanek
2008-11-09 10:52       ` Marcin Slusarz
2008-11-09 11:33         ` Lukas Hejtmanek
2008-11-09 13:24           ` Rafael J. Wysocki
2008-11-09 20:09             ` Lukas Hejtmanek
2008-11-09 20:28               ` Arjan van de Ven
2008-11-09 20:34                 ` Lukas Hejtmanek
2008-11-09 21:24                   ` Arjan van de Ven
2008-11-09 21:38                     ` Lukas Hejtmanek
2008-11-09 21:43                     ` Lukas Hejtmanek
2008-11-09 21:57                       ` Thomas Gleixner
2008-11-10  8:12                         ` Lukas Hejtmanek
2008-11-10 12:16                         ` Lukas Hejtmanek
2008-11-09 21:56                     ` Thomas Gleixner
2008-11-09 22:46                       ` Bernhard Schmidt
2008-11-09 22:53                       ` Frans Pop
2008-11-14  1:45                       ` Frans Pop
2008-11-15 17:16                         ` Frans Pop
2008-11-15 18:04                           ` Arjan van de Ven
2008-11-16 19:27                         ` [2.6.28-rc5] TSC sync error and high hrtimer_start (was: Bootup time regression from 2.6.27 to 2.6.28-rc3+) Frans Pop
2008-11-17  2:18                           ` Frans Pop
2008-11-10 13:45                     ` Bootup time regression from 2.6.27 to 2.6.28-rc3+ Yves-Alexis Perez
2008-11-11 17:33                       ` Len Brown
2008-11-09 20:39                 ` Linus Torvalds
2008-11-09 20:48                   ` Arjan van de Ven [this message]
2008-11-09 14:20       ` Frans Pop
2008-11-09 15:14         ` Lukas Hejtmanek

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=20081109124836.34a2c126@infradead.org \
    --to=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=xhejtman@ics.muni.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.