From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751444AbeA2IUv (ORCPT ); Mon, 29 Jan 2018 03:20:51 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:40899 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751256AbeA2IUu (ORCPT ); Mon, 29 Jan 2018 03:20:50 -0500 Date: Mon, 29 Jan 2018 09:20:48 +0100 From: Sebastian Sewior To: "Paul E. McKenney" Cc: Thomas Gleixner , LKML , Anna-Maria Gleixner , Peter Zijlstra , Ingo Molnar Subject: Re: [PATCH] hrtimer: Reset hrtimer cpu base proper on CPU hotplug Message-ID: <20180129082047.hash3pnhpztzcg22@linutronix.de> References: <20180126220917.GI3741@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180126220917.GI3741@linux.vnet.ibm.com> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-01-26 14:09:17 [-0800], Paul E. McKenney wrote: > find this one. ;-) But it did pass rcutorture testing for a great many > years, didn't it? :-/ It started to trigger better (or at all) on our test box with modprobe kvm_intel preemption_timer=n on the host kernel so maybe a completely unrelated change helped to trigger this. Sebastian