From: Andrew Morton <akpm@digeo.com>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, george@mvista.com,
James.Bottomley@SteelEye.com, shemminger@osdl.org, alex@ssi.bg
Subject: Re: [PATCH] linux-2.5.67_lost-tick-fix_A2
Date: Wed, 16 Apr 2003 16:02:57 -0700 [thread overview]
Message-ID: <20030416160257.1c7143c4.akpm@digeo.com> (raw)
In-Reply-To: <1050533210.1081.164.camel@w-jstultz2.beaverton.ibm.com>
john stultz <johnstul@us.ibm.com> wrote:
>
> On Wed, 2003-04-16 at 15:32, Andrew Morton wrote:
> > john stultz <johnstul@us.ibm.com> wrote:
> > >
> > > This patch fixes a race in the timer_interrupt code caused by
> > > detect_lost_tick().
> >
> > Does this also fix the problem which Alex identified?
>
> Nope. It just handles the detect_lost_tick() race and related problems
> w/ the PIT causing seq_lock reader starvation.
>
> I'm still looking over the preempt locking issue he pointed out.
>
> I'll likely send a more cautious version of the patch he already posted
> to you.
OK, thanks.
I'm rather buried in timer patches at present. It would be best if you could
test new work in the context of those patches.
They are at http://www.zip.com.au/~akpm/linux/patches/timers/
The applying order is
posix_timers-CLOCK_MONOTONIC-fix.patch
jiffies_to_timespec-fix.patch
do_timer_overflow-locking-fix.patch
lost-tick-fix.patch
next prev parent reply other threads:[~2003-04-16 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 22:02 [PATCH] linux-2.5.67_lost-tick-fix_A2 john stultz
2003-04-16 22:32 ` Andrew Morton
2003-04-16 22:46 ` john stultz
2003-04-16 23:02 ` Andrew Morton [this message]
2003-04-16 23:03 ` george anzinger
2003-04-16 23:21 ` john stultz
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=20030416160257.1c7143c4.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=James.Bottomley@SteelEye.com \
--cc=alex@ssi.bg \
--cc=george@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).