From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755951Ab0KASpU (ORCPT ); Mon, 1 Nov 2010 14:45:20 -0400 Received: from smtp-out-053.synserver.de ([212.40.180.53]:1163 "HELO smtp-out-053.synserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1754211Ab0KASpQ (ORCPT ); Mon, 1 Nov 2010 14:45:16 -0400 X-SynServer-TrustedSrc: 1 X-SynServer-AuthUser: markus@trippelsdorf.de X-SynServer-PPID: 8384 Date: Mon, 1 Nov 2010 19:45:12 +0100 From: Markus Trippelsdorf To: Thomas Gleixner Cc: Borislav Petkov , Borislav Petkov , john stultz , "linux-kernel@vger.kernel.org" , "hpa@linux.intel.com" , Ingo Molnar , "Herrmann3, Andreas" , "heiko.carstens@de.ibm.com" , "a.p.zijlstra@chello.nl" , "avi@redhat.com" , "mtosatti@redhat.com" Subject: Re: [bisected] Clocksource tsc unstable git Message-ID: <20101101184512.GA1589@arch.trippelsdorf.de> References: <1288120736.2645.9.camel@localhost> <20101027142622.GA1555@arch.trippelsdorf.de> <20101027182608.GA1580@arch.trippelsdorf.de> <20101029081831.GA7149@liondog.tnic> <20101029083013.GA1553@arch.trippelsdorf.de> <20101029102713.GA21125@aftab> <20101029170040.GJ21125@aftab> <20101029172631.GA23546@arch.trippelsdorf.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 . 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