[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200609110901.GZ19604@bombadil.infradead.org>
Date: Tue, 9 Jun 2020 04:09:01 -0700
From: Matthew Wilcox <willy@...radead.org>
To: Stanimir Varbanov <stanimir.varbanov@...aro.org>
Cc: linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-media@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-btrfs@...r.kernel.org, linux-acpi@...r.kernel.org,
netdev@...r.kernel.org, Joe Perches <joe@...ches.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jason Baron <jbaron@...mai.com>,
Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH v3 1/7] Documentation: dynamic-debug: Add description of
level bitmask
On Tue, Jun 09, 2020 at 01:45:58PM +0300, Stanimir Varbanov wrote:
> +level
> + The given level will be a bitmask ANDed with the level of the each ``pr_debug()``
> + callsite. This will allow to group debug messages and show only those of the
> + same level. The -p flag takes precedence over the given level. Note that we can
> + have up to five groups of debug messages.
That doesn't sound like a "level". printk has levels. If you ask for
"level 3" messages, you get messages from levels 0, 1, 2, and 3. These
seem like "types" or "groups" or something.
> + // enable all messages in file with 0x01 level bitmask
> + nullarbor:~ # echo -n 'file foo.c level 0x01 +p' >
> + <debugfs>/dynamic_debug/control
Powered by blists - more mailing lists