[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <557AF49C.7060702@redhat.com>
Date: Fri, 12 Jun 2015 11:02:52 -0400
From: Prarit Bhargava <prarit@...hat.com>
To: Dave Jones <davej@...emonkey.org.uk>,
John Stultz <john.stultz@...aro.org>,
linux-kernel@...r.kernel.org,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Richard Cochran <richardcochran@...il.com>,
Jan Kara <jack@...e.cz>, Jiri Bohac <jbohac@...e.cz>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Shuah Khan <shuahkh@....samsung.com>
Subject: Re: [PATCH 0/5 v2] Fixes for leapsecond expiring early ABS_TIME CLOCK_REALTIME
timers
On 06/12/2015 10:59 AM, Dave Jones wrote:
> On Fri, Jun 12, 2015 at 10:55:57AM -0400, Prarit Bhargava wrote:
>
> > > > This series has only had limited testing, so I wanted to send
> > > > it out for initial review and comment. Folks can grab this tree
> > > > via git for testing here:
> > > > https://git.linaro.org/people/john.stultz/linux.git dev/early-leap-timer
> > >
> > > Any idea how far back this reaches ? Ie, which longterm stable releases
> > > might be affected by this ?
> >
> > Likely occurs in any kernel after NOHZ was introduced.
>
> At least on 3.14, it seems to happen even if NOHZ is disabled.
Ouch. :(
I wonder if we've every synched the tick edge with the second edge. Your test
implies the answer is "no".
P.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists