From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751449AbdJEQQe (ORCPT ); Thu, 5 Oct 2017 12:16:34 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:34949 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751144AbdJEQQc (ORCPT ); Thu, 5 Oct 2017 12:16:32 -0400 Date: Thu, 5 Oct 2017 18:16:23 +0200 (CEST) From: Thomas Gleixner To: Julia Cartwright cc: Steven Rostedt , Arnaldo Carvalho de Melo , bigeasy@linutronix.de, linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, Arnaldo Carvalho de Melo , Clark Williams , Dean Luick , Dennis Dalessandro , Doug Ledford , Kaike Wan , Leon Romanovsky , linux-rdma@vger.kernel.org, Peter Zijlstra , Sebastian Andrzej Siewior , Sebastian Sanchez Subject: Re: [PATCH 1/2] IB/hfi1: Use preempt_{dis,en}able_nort() In-Reply-To: <20171005160535.GI647@jcartwri.amer.corp.natinst.com> Message-ID: References: <20171003154920.31566-1-acme@kernel.org> <20171003154920.31566-2-acme@kernel.org> <20171005141744.GC21185@jcartwri.amer.corp.natinst.com> <20171005153759.GG647@jcartwri.amer.corp.natinst.com> <20171005115539.7daafb66@gandalf.local.home> <20171005160535.GI647@jcartwri.amer.corp.natinst.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Oct 2017, Julia Cartwright wrote: > On Thu, Oct 05, 2017 at 11:55:39AM -0400, Steven Rostedt wrote: > > On Thu, 5 Oct 2017 10:37:59 -0500 > > Julia Cartwright wrote: > > > > > On Thu, Oct 05, 2017 at 05:27:30PM +0200, Thomas Gleixner wrote: > > > > On Thu, 5 Oct 2017, Julia Cartwright wrote: > > > > > On Tue, Oct 03, 2017 at 12:49:19PM -0300, Arnaldo Carvalho de Melo wrote: > > > > > > - preempt_disable(); > > > > > > + preempt_disable_nort(); > > > > > > this_cpu_inc(*sc->buffers_allocated); > > > > > > > > > > Have you tried this on RT w/ CONFIG_DEBUG_PREEMPT? I believe that the > > > > > this_cpu_* operations perform a preemption check, which we'd trip. > > > > > > > > Good point. Changing this to migrate_disable() would do the trick. > > > > > > Wouldn't we still trip the preempt check even with migration disabled? > > > In another thread I asked the same question: should the preemption > > > checks here be converted to migration-checks in RT? > > > > Is it a "preemption check"? > > Sorry if I was unclear, more precisely: the this_cpu_* family of > accessors, w/ CONFIG_DEBUG_PREEMPT currently spits out a warning when > the caller is invoked in a context where preemption is enabled. > > The check is shared w/ the smp_processor_id() check, as implemented in > lib/smp_processor_id.c. It effectively boils down to a check of > preempt_count() and irqs_disabled(). Except that on RT that check cares about the migrate disable state. You can invoke this_cpu_* and smp_processor_id() in preemptible/interruptible context because of: if (cpumask_equal(current->cpus_ptr, cpumask_of(this_cpu))) goto out; That's true even on mainline. But you are right that this check needs some update because migrate_disable() does not immediately update the allowed cpumask IIRC. Thanks, tglx