Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757429AbcDGTIR (ORCPT ); Thu, 7 Apr 2016 15:08:17 -0400 Received: from mail-wm0-f44.google.com ([74.125.82.44]:38324 "EHLO mail-wm0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756654AbcDGTIQ (ORCPT ); Thu, 7 Apr 2016 15:08:16 -0400 Message-ID: <1460056091.4435.64.camel@gmail.com> Subject: Re: [rfc patch 2/2] rt/locking/hotplug: Fix rt_spin_lock_slowlock() migrate_disable() bug From: Mike Galbraith To: Sebastian Andrzej Siewior Cc: Thomas Gleixner , linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, Steven Rostedt , Peter Zijlstra Date: Thu, 07 Apr 2016 21:08:11 +0200 In-Reply-To: <57068F78.2070607@linutronix.de> References: <1455318168-7125-1-git-send-email-bigeasy@linutronix.de> <1455318168-7125-4-git-send-email-bigeasy@linutronix.de> <1458463425.3908.5.camel@gmail.com> <1458814024.23732.35.camel@gmail.com> <1459405903.14336.64.camel@gmail.com> <20160401211105.GE29603@linutronix.de> <1459566735.3779.36.camel@gmail.com> <1459837988.26938.16.camel@gmail.com> <1459860597.7776.2.camel@gmail.com> <1459944021.3990.14.camel@gmail.com> <1460003831.3882.106.camel@gmail.com> <57068F78.2070607@linutronix.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 726 Lines: 17 On Thu, 2016-04-07 at 18:48 +0200, Sebastian Andrzej Siewior wrote: > On 04/07/2016 06:37 AM, Mike Galbraith wrote: > > On Wed, 2016-04-06 at 14:00 +0200, Mike Galbraith wrote: > > > It'll take a hotplug beating seemingly as well as any non-rt kernel, > > > but big box NAKed it due to jitter, which can mean 1.0 things.. duh. > > > > FWIW, the below turned big box NAK into ACK. Stressing hotplug over > > night, iteration completion time went from about 2 1/2 hours with > > bandaids on the two identified rt sore spots, to an hour and 10 minutes > > as well for some reason, but whatever.. > > Just to be clear. I need #1, #2 from this thread and this below to make > it work? The followup to 2/2 replaced 2/2. -Mike