public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: "Krzysztof Wilczyński" <kw@linux.com>
To: lirongqing <lirongqing@baidu.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: sysfs: Suppress FW_BUG warning when NUMA node already matches
Date: Sun, 15 Mar 2026 05:54:07 +0900	[thread overview]
Message-ID: <20260314205407.GB672783@rocinante> (raw)
In-Reply-To: <20260313050826.2126-1-lirongqing@baidu.com>

Hello,

> The numa_node sysfs interface allows users to manually override a PCI
> device's NUMA node assignment. Currently, every write triggers a
> FW_BUG warning and taints the kernel, even when writing the same value
> that is already set.

So, this works as intended, then?

What makes multiple writes to this sysfs attribute, if you don't mind me
asking?  Do you have some tool that does this?  Some automation?

Especially, that you seem to be writing the same value over and over.

>  	if (node != NUMA_NO_NODE && !node_online(node))
>  		return -EINVAL;
>  
> -	add_taint(TAINT_FIRMWARE_WORKAROUND, LOCKDEP_STILL_OK);
> -	pci_alert(pdev, FW_BUG "Overriding NUMA node to %d.  Contact your vendor for updates.",
> -		  node);
> +	if (node != dev->numa_node) {
> +		add_taint(TAINT_FIRMWARE_WORKAROUND, LOCKDEP_STILL_OK);
> +		pci_alert(pdev, FW_BUG "Overriding NUMA node to %d.  Contact your vendor for updates.",
> +			  node);
> +		dev->numa_node = node;
> +	}

You could invert the check and make it an early return where you just
return count.  Would save on the new indent level.

Thank you!

	Krzysztof

  reply	other threads:[~2026-03-14 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13  5:08 [PATCH] PCI: sysfs: Suppress FW_BUG warning when NUMA node already matches lirongqing
2026-03-14 20:54 ` Krzysztof Wilczyński [this message]
2026-03-16  2:20   ` 答复: [????] " Li,Rongqing(ACG CCN)
2026-03-16  3:12     ` Krzysztof Wilczy��ski

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=20260314205407.GB672783@rocinante \
    --to=kw@linux.com \
    --cc=bhelgaas@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lirongqing@baidu.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