[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1010291932090.2692@localhost6.localdomain6>
Date: Fri, 29 Oct 2010 19:34:35 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Borislav Petkov <bp@...64.org>
cc: Markus Trippelsdorf <markus@...ppelsdorf.de>,
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
Boris,
On Fri, 29 Oct 2010, 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.
can you please check with your hardware folks? If we can't get some
affirmative info about that then we'd be forced to revert that commit
(if it turns out to be the culprit one). That'd be a pity as it would
bring back the full IO access penalty to everyone.
Thanks,
tglx
--
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