mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Justin Madru <jdm64@gawab.com>
Cc: Greg KH <gregkh@suse.de>, Ingo Molnar <mingo@elte.hu>,
	lkml <linux-kernel@vger.kernel.org>,
	Michal Januszewski <spock@gentoo.org>,
	Antonino Daplas <adaplas@gmail.com>, Rafael Wysocki <rjw@sisk.pl>,
	Romano Giannetti <romano.giannetti@gmail.com>,
	Adrian Bunk <bunk@kernel.org>,
	Jeremy Nickurak <kernel-bugs@atrus.rifetech.com>
Subject: Re: [PATCH] sched: disable hrtick implementation
Date: Wed, 20 Aug 2008 09:24:51 +0200	[thread overview]
Message-ID: <1219217091.10800.395.camel@twins> (raw)
In-Reply-To: <48AB4F2B.9070405@gawab.com>

On Tue, 2008-08-19 at 15:54 -0700, Justin Madru wrote:
> The hrtick implementation in 2.6.25 and .26 has been known to cause boot
> problems with at least Intel GMA cards. see:
> 
>  https://bugs.freedesktop.org/show_bug.cgi?id=15602
>  http://bugzilla.kernel.org/show_bug.cgi?id=10892
> 
> A full fix to hrtick went into 2.6.27 
> (31656519e132f6612584815f128c83976a9aaaef),
> but that fix is too intrusive to backport. Henceforth, we default to 
> disable hrtick.

Thing is, I'm still not understanding how, or if, the old code is wrong.

That said, this will paper over the problem just fine, and as its old
kernels we're talking about I don't particularly care.

Just occured to me that a Kconfig change that always makes
CONFIG_SCHED_HRTICK not set will also do.

> Signed-off-by: Justin Madru <jdm64@gawab.com>
> Tested-by: Justin Madru <jdm64@gawab.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Ingo Molnar <mingo@elte.hu>
> 
> --- a/kernel/sched_features.h
> +++ b/kernel/sched_features.h
> @@ -4,7 +4,7 @@
>  SCHED_FEAT(AFFINE_WAKEUPS, 1)
>  SCHED_FEAT(CACHE_HOT_BUDDY, 1)
>  SCHED_FEAT(SYNC_WAKEUPS, 1)
> -SCHED_FEAT(HRTICK, 1)
> +SCHED_FEAT(HRTICK, 0)
>  SCHED_FEAT(DOUBLE_TICK, 0)
>  SCHED_FEAT(NORMALIZED_SLEEPER, 1)
>  SCHED_FEAT(DEADLINE, 1)
> 


  reply	other threads:[~2008-08-20  7:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 18:21 Backport hr-tick fix into .25/.26 Justin Madru
2008-08-19  0:31 ` Ingo Molnar
2008-08-19  2:43   ` Justin Madru
2008-08-19  6:28   ` Peter Zijlstra
2008-08-19  9:25     ` Ingo Molnar
2008-08-19  9:33       ` Peter Zijlstra
2008-08-19 18:22         ` Greg KH
2008-08-19 19:30           ` Justin Madru
2008-08-19 19:44             ` Greg KH
2008-08-19 22:54               ` [PATCH] sched: disable hrtick implementation Justin Madru
2008-08-20  7:24                 ` Peter Zijlstra [this message]
2008-08-20 18:43                   ` Justin Madru

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=1219217091.10800.395.camel@twins \
    --to=peterz@infradead.org \
    --cc=adaplas@gmail.com \
    --cc=bunk@kernel.org \
    --cc=gregkh@suse.de \
    --cc=jdm64@gawab.com \
    --cc=kernel-bugs@atrus.rifetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=romano.giannetti@gmail.com \
    --cc=spock@gentoo.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®