All of lore.kernel.org
 help / color / mirror / Atom feed
From: dmkhn@proton.me
To: Jan Beulich <jbeulich@suse.com>
Cc: Julien Grall <julien@xen.org>,
	andrew.cooper3@citrix.com, anthony.perard@vates.tech,
	michal.orzel@amd.com, roger.pau@citrix.com,
	sstabellini@kernel.org, dmukhin@ford.com,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v1] xen/console: remove __printk_ratelimit()
Date: Wed, 30 Jul 2025 18:06:27 +0000	[thread overview]
Message-ID: <aIpfH5Cy10o8VMCu@kraken> (raw)
In-Reply-To: <4292abbe-28b1-4545-87af-b37dd4ace53e@suse.com>

On Wed, Jul 30, 2025 at 07:35:04AM +0200, Jan Beulich wrote:
> On 30.07.2025 00:18, dmkhn@proton.me wrote:
> > On Mon, Jul 28, 2025 at 11:32:43AM +0200, Jan Beulich wrote:
> >> On 26.07.2025 11:20, Julien Grall wrote:
> >>> On 25/07/2025 22:24, dmkhn@proton.me wrote:
> >>>> From: Denis Mukhin <dmukhin@ford.com>
> >>>>
> >>>> __printk_ratelimit() is never used outside of the console driver.
> >>>> Remove it from the lib.h and merge with the public printk_ratelimit().
> >>>
> >>> Is this solving any sort of violation? Asking because even if the
> >>> function is only used by one caller, I could see a benefit to be able to
> >>> use different value for the ratelimit. So I leaning towards keep the
> >>> code as-is.
> >>
> >> +1
> >>
> >> In fact I'm surprised (or maybe not) that we still don't make better use
> >> the rate limiting functionality.
> >
> > Out of curiosity, do you have any ideas re: make better use of the rate
> > limiting functionality?
> 
> No concrete ones; thinking about this has been way too long ago.
> 
> > Build-time parameterization?
> 
> That and/or command line controls.

Got it.

Can you please explain why exporting __printk_ratelimit() is still required
for implementation of build/command line settings in console.c?

> 
> Jan



  reply	other threads:[~2025-07-30 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25 21:24 [PATCH v1] xen/console: remove __printk_ratelimit() dmkhn
2025-07-26  9:20 ` Julien Grall
2025-07-26 20:56   ` dmkhn
2025-07-28  9:32   ` Jan Beulich
2025-07-29 22:18     ` dmkhn
2025-07-30  5:35       ` Jan Beulich
2025-07-30 18:06         ` dmkhn [this message]
2025-07-31  6:23           ` Jan Beulich
2025-07-31 21:28             ` dmkhn
2025-08-01  7:32               ` Jan Beulich
2025-08-06 11:09 ` Roger Pau Monné

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=aIpfH5Cy10o8VMCu@kraken \
    --to=dmkhn@proton.me \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=dmukhin@ford.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.