linux-kernel - Re: [PATCH] PCI: dwc: Separate MSI out to different controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250211075654.zxjownqe5guwzdlf@thinkpad>
Date: Tue, 11 Feb 2025 13:26:54 +0530
From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
To: Tsai Sung-Fu <danielsftsai@...gle.com>
Cc: Jingoo Han <jingoohan1@...il.com>,
	Lorenzo Pieralisi <lpieralisi@...nel.org>,
	Krzysztof Wilczyński <kw@...ux.com>,
	Rob Herring <robh@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	Brian Norris <briannorris@...gle.com>,
	Andrew Chant <achant@...gle.com>, Sajid Dalvi <sdalvi@...gle.com>
Subject: Re: [PATCH] PCI: dwc: Separate MSI out to different controller

On Tue, Feb 11, 2025 at 03:16:11PM +0800, Tsai Sung-Fu wrote:
> Hi Mani and Bjorn,
> 
> Sorry for the late reply, we just found out some problems in the patch
> we are trying to upstream here, and figuring out it might not be a
> good idea to keep this process going, so I would drop this patch
> submission, and come back once we figure it out a better way.
> 
> BTW, May I ask why upstream chose to flag this driver with
> MSI_FLAG_NO_AFFINITY and remove the function dw_pci_msi_set_affinity
> implementation ?
> 

Because you cannot set affinity for chained MSIs as these MSIs are muxed to
another parent interrupt. Since the IRQ affinity is all about changing which CPU
gets the IRQ, affinity setting is only possible for the MSI parent.

- Mani

-- 
மணிவண்ணன் சதாசிவம்