From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752897AbcHNRal (ORCPT ); Sun, 14 Aug 2016 13:30:41 -0400 Received: from smtprelay0143.hostedemail.com ([216.40.44.143]:56736 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752356AbcHNRaj (ORCPT ); Sun, 14 Aug 2016 13:30:39 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::::,RULES_HIT:41:355:379:541:599:960:973:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1541:1593:1594:1711:1730:1747:1777:1792:2393:2559:2562:2828:3138:3139:3140:3141:3142:3352:3622:3865:3867:3868:3870:3871:3873:3874:4321:5007:7903:10004:10400:10848:11232:11658:11914:12517:12519:12740:13069:13073:13095:13311:13357:13439:13894:14659:21080:21324:21433:21451:30012:30051:30054:30064:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:1,LUA_SUMMARY:none X-HE-Tag: push29_732810d6a4846 X-Filterd-Recvd-Size: 2456 Message-ID: <1471195790.4075.45.camel@perches.com> Subject: Re: [PATCH 0/2] be2iscsi: Logging neatening From: Joe Perches To: Bart Van Assche , Christophe JAILLET , "linux-scsi@vger.kernel.org" Cc: Jayamohan Kallickal , Ketan Mukadam , John Soni Jose , "James E.J. Bottomley" , "Martin K. Petersen" , "linux-kernel@vger.kernel.org" Date: Sun, 14 Aug 2016 10:29:50 -0700 In-Reply-To: References: <1471107782.3467.28.camel@perches.com> <1471191843.4075.39.camel@perches.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.2-0ubuntu3 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 2016-08-14 at 17:09 +0000, Bart Van Assche wrote: > My primary concern is how to enable and disable log messages from user  > space. Many drivers define their own logging macros and export a bitmask  > that allows to enable and disable logging messages per category. These  > bitmask control mechanisms are annoying because figuring out what bit  > controls which message category requires a search through the driver  > source code. I'd like to see all these custom logging macros disappear  > and being replaced by a single mechanism. The "dynamic debug" mechanism  > e.g. is in my opinion much easier to use than the different custom  > logging mechanisms. Dynamic debug doesn't have a bitmask function and still requires looking through the code for lines and format strings. I think you are looking for a system wide equivalent for the ethtool/netif_ mechanism. Nothing like that exists currently. Some code uses a bitmask/and, other code uses a level/comparison. Care to propose something?