lkml.org 
[lkml]   [2008]   [Aug]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Backport hr-tick fix into .25/.26
From
Date
On Tue, 2008-08-19 at 11:25 +0200, Ingo Molnar wrote:
> * Peter Zijlstra <peterz@infradead.org> wrote:
>
> > On Tue, 2008-08-19 at 02:31 +0200, Ingo Molnar wrote:
> > > * Justin Madru <jdm64@gawab.com> wrote:
> > >
> > > > This commit introduced the bug.
> > > > commit 8f4d37ec073c17e2d4aa8851df5837d798606d6f
> > > > sched: high-res preemption tick
> > >
> > > > And this one fixed it
> > > >
> > > > commit 31656519e132f6612584815f128c83976a9aaaef
> > > > sched, x86: clean up hrtick implementation
> > >
> > > hm, the backport of 31656519 is a bit intrusive.
> > >
> > > find below is an (untested!) version of it - i havent even build-tested
> > > it. Does it work for you? But this is Greg's call really.
> > >
> >
> > It largely depends on all the new IPI stuff that went into 27 as well,
> > so I'd be surprised if its easily backportable..
>
> ah, i see. How about a simple patch then that disables hrtick [given
> that it's now fixed .27 but the fix is too intrusive to backport]? Would
> that be too risky for -stable?

That's just flipping sched_feat(HRTICK) to 0 by default.



\
 
 \ /
  Last update: 2008-08-19 11:35    [W:0.438 / U:0.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site