From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 2DAC8C433F5 for ; Thu, 28 Apr 2022 05:52:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=LjWmhnHzMcxy17z65hUa3Ta2+s7YvwfFsocSbfa5tfg=; b=hclu4mdUu52bBu ay47odvKfaa8qDdhTCy1n9AqG4DwdRwMtvE3cd6TPBkICQdgKUwBc3GWBKW6paun7W+lD9JXgf7pd CTvYGggqQCut5z9SmLGvF5CiQPIrF99Qme3EmNBBKVci5P/1V3n6bPanz9nFblUfyyY+ebxFOIkuq 7uppu5evaZfXnJ6TwPMlLKnsbSrijAlubSGFQ12QA4d9ii0gi6Km6aEFzqur3ylWfZjn9A3y7WDka raWuLW7GQlHL5n3GpQNN2k2ifhu3ax9hjPGSpqs8ubNzeXPcoIcAhhMtYNmtvzjoGEaUG4cZNJNTE II0zemDDCyVpSH2oZi6g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1njx4B-004nGs-RO; Thu, 28 Apr 2022 05:51:51 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1njx48-004nG8-Ho for linux-arm-kernel@lists.infradead.org; Thu, 28 Apr 2022 05:51:49 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B373B61CD2; Thu, 28 Apr 2022 05:51:47 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0DB6BC385A9; Thu, 28 Apr 2022 05:51:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1651125106; bh=BL/ztcIdTOHAttqORil3BUGJFYSYBXhS93ayc6l+nXE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=2rK9PWY7j41JX0nmeJkE6BBYRs1hKWOhGXMrtGRYSB8txFNFL3XlocI6+ubQ/O+8J t/DragmyB5XIeryU9mwNV9Fm0GJEA7fqErUp42mLVkCLZ8+SRzskjqgHOchg3WdaiK hLMSHBjS85b+PVwAFaAJJMJuu6PhU3Au1bOEGx5U= Date: Thu, 28 Apr 2022 07:51:39 +0200 From: Greg KH To: Sai Prakash Ranjan Cc: arnd@arndb.de, catalin.marinas@arm.com, rostedt@goodmis.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, maz@kernel.org, quic_psodagud@quicinc.com, quic_tsoni@quicinc.com, will@kernel.org Subject: Re: [PATCHv11 6/6] asm-generic/io: Add logging support for MMIO accessors Message-ID: References: <3de35c9f4a3a070d197bab499acefc709a6f5336.1645772606.git.quic_saipraka@quicinc.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <3de35c9f4a3a070d197bab499acefc709a6f5336.1645772606.git.quic_saipraka@quicinc.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220427_225148_664931_75AAAA1E X-CRM114-Status: GOOD ( 14.22 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Apr 28, 2022 at 09:00:13AM +0530, Sai Prakash Ranjan wrote: > Add logging support for MMIO high level accessors such as read{b,w,l,q} > and their relaxed versions to aid in debugging unexpected crashes/hangs > caused by the corresponding MMIO operation. Also add a generic flag > (__DISABLE_TRACE_MMIO__) which is used to disable MMIO tracing in nVHE KVM > and if required can be used to disable MMIO tracing for specific drivers. This "add a build flag to a Makefile to change how a driver operates" feels very wrong to me given that this is now a totally new way to control how a driver works at build time. That's not anything we have done before for drivers and if added, is only going to create much added complexity. How about requiring that the #define be in the .c files, and not in the Makefile, as Makefile changes are much much harder to notice and review over time. Also, I see that this "disable the trace" feature has already been asked for for 2 other drivers in the Android kernel tree, why not include those changes here as well? That kind of shows that this new feature is limited in that driver authors are already wanting it disabled, even before it is accepted. Because of that, who _will_ be using this feature? thanks, greg k-h _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel