From mboxrd@z Thu Jan  1 00:00:00 1970
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753309AbeAFXVL (ORCPT <rfc822;ralf@linux-mips.org> + 1 other);
        Sat, 6 Jan 2018 18:21:11 -0500
Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:40330 "EHLO
        mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL)
        by vger.kernel.org with ESMTP id S1752613AbeAFXVK (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sat, 6 Jan 2018 18:21:10 -0500
Date: Sat, 6 Jan 2018 15:21:44 -0800
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
        Anna-Maria Gleixner <anna-maria@linutronix.de>,
        Sebastian Siewior <bigeasy@linutronix.de>,
        Peter Zijlstra <peterz@infradead.org>,
        Frederic Weisbecker <fweisbec@gmail.com>,
        Ingo Molnar <mingo@kernel.org>
Subject: Re: [patch 0/4] timer/nohz: Fix timer/nohz woes
Reply-To: paulmck@linux.vnet.ibm.com
References: <20171222145111.919609918@linutronix.de>
 <20171222170907.GJ7829@linux.vnet.ibm.com>
 <20171224012120.GA4113@linux.vnet.ibm.com>
 <20171224012924.GA6916@linux.vnet.ibm.com>
 <20180105194150.GA24831@linux.vnet.ibm.com>
 <alpine.DEB.2.20.1801062215570.2376@nanos>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.20.1801062215570.2376@nanos>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-TM-AS-GCONF: 00
x-cbid: 18010623-0048-0000-0000-0000021FDC85
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00008330; HX=3.00000241; KW=3.00000007;
 PH=3.00000004; SC=3.00000244; SDB=6.00971257; UDB=6.00491938; IPR=6.00751211;
 BA=6.00005765; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000;
 ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00018911; XFM=3.00000015;
 UTC=2018-01-06 23:21:07
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 18010623-0049-0000-0000-000043AE7E59
Message-Id: <20180106232144.GB9671@linux.vnet.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-01-06_14:,,
 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501
 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0
 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0
 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1709140000
 definitions=main-1801060337
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Return-Path: <linux-kernel-owner@vger.kernel.org>

On Sat, Jan 06, 2018 at 10:18:40PM +0100, Thomas Gleixner wrote:
> On Fri, 5 Jan 2018, Paul E. McKenney wrote:
> > But after more than 1,000 hours of test runs, split roughly evenly
> > among the above three scenarios, there is no statistically significant
> > difference in error rate among them.  This means that there is some
> > other bug lurking somewhere, and having the same appearance (lost timer).
> > Were you guys ever able to reproduce this via rcutorture?
> 
> No.

I was afraid of that...  ;-)

> We'll setup more testing on Monday. Which of the tests fails or at least
> exposes the highest failure rate?

TREE01, as in:

bash tools/testing/selftests/rcutorture/bin/kvm.sh --cpus 48 --duration 180 --configs "42*TREE01"

This results in 42 runs of TREE01 consuming about 21 hours of wall-clock
time.  (Each run of TREE01 uses 8 CPUs.)

							Thanx, Paul