From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752055Ab1ITRPz (ORCPT ); Tue, 20 Sep 2011 13:15:55 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.122]:42095 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750871Ab1ITRPy (ORCPT ); Tue, 20 Sep 2011 13:15:54 -0400 X-Authority-Analysis: v=1.1 cv=agqPq5NoKwAPC9P66H7dbYUCjxvmT73as08i4x3aqAA= c=1 sm=0 a=3kNrfhY1ZosA:10 a=5SG0PmZfjMsA:10 a=Q9fys5e9bTEA:10 a=17wjrS5wAhQaEczCPkpxpQ==:17 a=KXYxzh5JGYT-Pe7eDaYA:9 a=PUjeQqilurYA:10 a=17wjrS5wAhQaEczCPkpxpQ==:117 X-Cloudmark-Score: 0 X-Originating-IP: 74.67.83.30 Subject: Re: [RFC][PATCH 0/5] Introduce checks for preemptable code for this_cpu_read/write() From: Steven Rostedt To: Peter Zijlstra Cc: Christoph Lameter , Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org, Ingo Molnar , Andrew Morton , Thomas Gleixner , Mathieu Desnoyers In-Reply-To: <1316538541.13664.60.camel@twins> References: <20110919212040.745370781@goodmis.org> <1316487977.29966.32.camel@gandalf.stny.rr.com> <27409.1316522696@turing-police.cc.vt.edu> <1316531987.29966.65.camel@gandalf.stny.rr.com> <1316536260.29966.93.camel@gandalf.stny.rr.com> <1316537808.29966.98.camel@gandalf.stny.rr.com> <1316538541.13664.60.camel@twins> Content-Type: text/plain; charset="ISO-8859-15" Date: Tue, 20 Sep 2011 13:15:52 -0400 Message-ID: <1316538952.29966.105.camel@gandalf.stny.rr.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2011-09-20 at 19:09 +0200, Peter Zijlstra wrote: > On Tue, 2011-09-20 at 12:56 -0400, Steven Rostedt wrote: > > random_cpu_*() // Thomas's idea > > I like this one best.. I like it too, but not really the most appropriate. > > But you forgot do deal with the irqsafe_cpu() crap, that's the same > brainfart as this_cpu() but more expensive because it frobs IRQ state. But irqsafe_cpu_*() doesn't really have any real meaning to me. That is something when I see it, I go and read the comments about it. It doesn't contain "this_cpu" which is something that seems to explain what it is, even though the obvious is not what it is. -- Steve