From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934738AbeD0OhD (ORCPT ); Fri, 27 Apr 2018 10:37:03 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:41198 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932733AbeD0OhA (ORCPT ); Fri, 27 Apr 2018 10:37:00 -0400 Date: Fri, 27 Apr 2018 15:37:20 +0100 From: Will Deacon To: Kim Phillips Cc: Mark Rutland , Ganapatrao Kulkarni , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, jnair@caviumnetworks.com, Robert.Richter@cavium.com, Vadim.Lomovtsev@cavium.com, Jan.Glauber@cavium.com, gklkml16@gmail.com Subject: Re: [PATCH v4 2/2] ThunderX2: Add Cavium ThunderX2 SoC UNCORE PMU driver Message-ID: <20180427143719.GA5093@arm.com> References: <20180425090047.6485-1-ganapatrao.kulkarni@cavium.com> <20180425090047.6485-3-ganapatrao.kulkarni@cavium.com> <20180426170624.bfcba885431d57d0de2a3ddd@arm.com> <20180427093027.ngtuoezyh6mtz26p@lakrids.cambridge.arm.com> <20180427081525.f9dcc756678baf3bb6e6e473@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180427081525.f9dcc756678baf3bb6e6e473@arm.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 27, 2018 at 08:15:25AM -0500, Kim Phillips wrote: > On Fri, 27 Apr 2018 10:30:27 +0100 > Mark Rutland wrote: > > On Thu, Apr 26, 2018 at 05:06:24PM -0500, Kim Phillips wrote: > > > On Wed, 25 Apr 2018 14:30:47 +0530 > > > Ganapatrao Kulkarni wrote: > > > > > > > +static int thunderx2_uncore_event_init(struct perf_event *event) > > > > > This PMU driver can be made more user-friendly by not just silently > > > returning an error code such as -EINVAL, but by emitting a useful > > > message describing the specific error via dmesg. > > > > As has previously been discussed on several occasions, patches which log > > to dmesg in a pmu::event_init() path at any level above pr_debug() are > > not acceptable -- dmesg is not intended as a mechanism to inform users > > of driver-specific constraints. > > I disagree - drivers do it all the time, using dev_err(), dev_warn(), etc. > > > I would appreciate if in future you could qualify your suggestion with > > the requirement that pr_debug() is used. > > It shouldn't - the driver isn't being debugged, it's in regular use. For anything under drivers/perf/, I'd prefer not to have these prints and instead see efforts to improve error reporting via the perf system call interface. Anyway, I think this driver has bigger problems that need addressing. Will