linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@akamai.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Raymond Bennett <raymond.bennett@gmail.com>,
	linux-edac@vger.kernel.org, Jim Cromie <jim.cromie@gmail.com>
Subject: Re: Constant output in syslog of EDAC message
Date: Mon, 26 Oct 2020 16:52:06 -0400	[thread overview]
Message-ID: <e698aaa3-2a3e-acdd-6ffe-d3275f7e7346@akamai.com> (raw)
In-Reply-To: <20201026181043.GF22116@zn.tnic>



On 10/26/20 2:10 PM, Borislav Petkov wrote:
> Hi,
> 
> On Mon, Oct 26, 2020 at 01:47:05PM -0400, Jason Baron wrote:
>> So, we would still continue to support edac_debug_level=N but the
>> user would have additional control.
> 
> Do you have any actual users needing this? If yes, what are their use
> cases?
> 
> Because I have this aversion towards adding functionality just because
> and that it potentially might be useful and "users may want". Either
> they do and they want to use it for X or we don't do anything... yet.
> 
> In this particular example, those debug printks are just useless noise
> so off they go.
> 
> Thx.
> 

Hi Boris,

So I was motivated by this example, where if we had this facility,
we could easily say just go turn off that specific print instead of
wait for a new kernel. More generally, I think as you crank up the
verbosity there may be more of a need to customize the debug
information, but I don't have any specific use case in mind beyond
that.

I was also curious if various subsystems would find this facility
useful.

Thanks,

-Jason

      reply	other threads:[~2020-10-26 21:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 20:37 Constant output in syslog of EDAC message Raymond Bennett
2020-10-19 20:56 ` Borislav Petkov
2020-10-19 21:25   ` Jason Baron
2020-10-20  9:19     ` Borislav Petkov
2020-10-26 12:04       ` [PATCH] EDAC: Do not issue useless debug statements in the polling routine Borislav Petkov
2020-10-26 17:47       ` Constant output in syslog of EDAC message Jason Baron
2020-10-26 18:10         ` Borislav Petkov
2020-10-26 20:52           ` Jason Baron [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e698aaa3-2a3e-acdd-6ffe-d3275f7e7346@akamai.com \
    --to=jbaron@akamai.com \
    --cc=bp@alien8.de \
    --cc=jim.cromie@gmail.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=raymond.bennett@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).