From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752319AbaB1U6e (ORCPT ); Fri, 28 Feb 2014 15:58:34 -0500 Received: from merlin.infradead.org ([205.233.59.134]:42458 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751646AbaB1U6d (ORCPT ); Fri, 28 Feb 2014 15:58:33 -0500 Date: Fri, 28 Feb 2014 21:58:28 +0100 From: Peter Zijlstra To: Steven Rostedt Cc: "H. Peter Anvin" , Vince Weaver , Linux Kernel , Ingo Molnar , Jiri Olsa , Arnaldo Carvalho de Melo Subject: Re: [PATCH] x86: Rename copy_from_user_nmi() to copy_from_user_trace() Message-ID: <20140228205828.GE14089@laptop.programming.kicks-ass.net> References: <20140228092341.12a40f7c@gandalf.local.home> <1c583986-74f8-4829-883b-390dc49ddabb@email.android.com> <20140228154026.GH9987@twins.programming.kicks-ass.net> <5310B60F.30806@zytor.com> <20140228112946.1f194397@gandalf.local.home> <20140228143316.211d4034@gandalf.local.home> <20140228204621.GA14089@laptop.programming.kicks-ass.net> <20140228155130.26adcef3@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140228155130.26adcef3@gandalf.local.home> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 28, 2014 at 03:51:30PM -0500, Steven Rostedt wrote: > On Fri, 28 Feb 2014 21:46:21 +0100 > Peter Zijlstra wrote: > > > On Fri, Feb 28, 2014 at 02:33:16PM -0500, Steven Rostedt wrote: > > > [ H. Peter, Here's the rename patch. I did not include your update. You > > > can add that first and then massage this patch on top. But this isn't > > > critical for mainline or stable, where as I believe your patch is. ] > > > > > > The tracing utilities sometimes need to read from userspace (stack tracing), > > > and to do this it has as special copy_from_user function called > > > copy_from_user_nmi(). Well, as tracers can call this from outside of > > > nmi context, the "_nmi" part is a misnomer and "_trace" is a better > > > name. > > > > NAK, spin_lock_irq() is very much an IRQ safe lock. Similarly > > copy_from_user_nmi() is an NMI safe copy from user. > > > > Furthermore, there's exactly 0 trace users, so the proposed name is > > actively worse. > > Heh, I consider perf and oprofile special tracers ;-) They're first and foremost profilers; which is an entirely different thing. But other people seem to get confused on this distinction too.