[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101101184512.GA1589@arch.trippelsdorf.de>
Date: Mon, 1 Nov 2010 19:45:12 +0100
From: Markus Trippelsdorf <markus@...ppelsdorf.de>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Borislav Petkov <bp@...64.org>, Borislav Petkov <bp@...en8.de>,
john stultz <johnstul@...ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
Ingo Molnar <mingo@...e.hu>,
"Herrmann3, Andreas" <Andreas.Herrmann3@....com>,
"heiko.carstens@...ibm.com" <heiko.carstens@...ibm.com>,
"a.p.zijlstra@...llo.nl" <a.p.zijlstra@...llo.nl>,
"avi@...hat.com" <avi@...hat.com>,
"mtosatti@...hat.com" <mtosatti@...hat.com>
Subject: Re: [bisected] Clocksource tsc unstable git
On Mon, Nov 01, 2010 at 07:05:17PM +0100, Thomas Gleixner wrote:
> On Fri, 29 Oct 2010, Markus Trippelsdorf wrote:
> > On Fri, Oct 29, 2010 at 07:00:40PM +0200, Borislav Petkov wrote:
> > > So Markus, can you try with 995bd3bb5c78, but by increasing the value
> > > to, say 16 (I don't know what's a good value here, let's double the old
> > > one). Simply change the line
> > >
> > > return res < 8 ? -ETIME : 0;
> > >
> > > to
> > >
> > > return res < 16 ? -ETIME : 0;
> > >
> > >
> > > in <arch/x86/kernel/hpet.c:hpet_next_event()>. I'll do that too on the
> > > machine here when I get around to it.
> >
> > Yes, I already did this, although I'm running
> > return res < 12 ? -ETIME : 0;
> > at the moment.
>
> Any update on this ?
Yes, it runs stable thus far. No "slowdowns", no problems.
--
Markus
--
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