From: Lijun Pan <lijun.pan@intel.com>
To: Fenghua Yu <fenghua.yu@intel.com>, Vinod Koul <vkoul@kernel.org>,
<dmaengine@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Dave Jiang <dave.jiang@intel.com>,
Sanjay Kumar <sanjay.k.kumar@intel.com>
Subject: Re: [PATCH] dmaengine: idxd: rate limit printk in misc interrupt thread
Date: Tue, 26 Sep 2023 11:30:53 -0500 [thread overview]
Message-ID: <8199226c-9642-e089-8dce-64ac8483efea@intel.com> (raw)
In-Reply-To: <20230924002347.1117757-1-fenghua.yu@intel.com>
On 9/23/2023 7:23 PM, Fenghua Yu wrote:
> From: Dave Jiang <dave.jiang@intel.com>
>
> Add rate limit to the dev_warn() call in the misc interrupt thread. This
> limits dmesg getting spammed if a descriptor submitter is spamming bad
> descriptors with invalid completion records and resulting the errors being
> continuously reported by the misc interrupt handling thread.
>
> Reported-by: Sanjay Kumar <sanjay.k.kumar@intel.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> Reviewed-by: Fenghua Yu <fenghua.yu@intel.com>
> ---
Acked-by: Lijun Pan <lijun.pan@intel.com>
>
> This patch was sent to dmaengine mailing list before:
> https://lore.kernel.org/all/165125377735.312075.15715853788802098990.stgit@djiang5-desk3.ch.intel.com/
> But it hasn't be merged into upstream yet. Add my Reviewed-by tag
> and re-send it. No code or commit message change.
>
> drivers/dma/idxd/irq.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dma/idxd/irq.c b/drivers/dma/idxd/irq.c
> index 041be6a4dec4..8e895a1e1881 100644
> --- a/drivers/dma/idxd/irq.c
> +++ b/drivers/dma/idxd/irq.c
> @@ -430,8 +430,8 @@ irqreturn_t idxd_misc_thread(int vec, void *data)
> val |= IDXD_INTC_ERR;
>
> for (i = 0; i < 4; i++)
> - dev_warn(dev, "err[%d]: %#16.16llx\n",
> - i, idxd->sw_err.bits[i]);
> + dev_warn_ratelimited(dev, "err[%d]: %#16.16llx\n",
> + i, idxd->sw_err.bits[i]);
> err = true;
> }
>
next prev parent reply other threads:[~2023-09-26 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 0:23 [PATCH] dmaengine: idxd: rate limit printk in misc interrupt thread Fenghua Yu
2023-09-26 16:30 ` Lijun Pan [this message]
2023-09-28 11:56 ` Vinod Koul
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=8199226c-9642-e089-8dce-64ac8483efea@intel.com \
--to=lijun.pan@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sanjay.k.kumar@intel.com \
--cc=vkoul@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox