From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Justin Madru <jdm64@gawab.com>,
lkml <linux-kernel@vger.kernel.org>,
Michal Januszewski <spock@gentoo.org>,
Antonino Daplas <adaplas@gmail.com>, Greg KH <gregkh@suse.de>,
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: Backport hr-tick fix into .25/.26
Date: Tue, 19 Aug 2008 11:25:43 +0200 [thread overview]
Message-ID: <20080819092543.GD28713@elte.hu> (raw)
In-Reply-To: <1219127296.10800.357.camel@twins>
* 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?
Ingo
next prev parent reply other threads:[~2008-08-19 9:27 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 [this message]
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
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=20080819092543.GD28713@elte.hu \
--to=mingo@elte.hu \
--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=peterz@infradead.org \
--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 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.