linux-kernel - Affinity on non MSI-X interrupts

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>] [day] [month] [year] [list]

Message-ID: <714a8d82-c4b0-9661-5b78-ed0d87a0a5fc@gmail.com>
Date:   Sat, 24 Feb 2018 00:47:00 +0530
From:   valmiki <valmikibow@...il.com>
To:     linux-pci <linux-pci@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:     Bjorn Helgaas <helgaas@...nel.org>, sbodomerle@...il.com,
        rjui@...adcom.com
Subject: Affinity on non MSI-X interrupts

Hi,

Does multi MSI interrupts will also be set and routed by affinity ?

In drivers/pci/host/pcie-iproc-msi.c interrupt handler there is do while 
loop.
head = iproc_msi_read_reg(msi, IPROC_MSI_EQ_HEAD,
				  eq) & IPROC_MSI_EQ_MASK;
	do {
		tail = iproc_msi_read_reg(msi, IPROC_MSI_EQ_TAIL,
					  eq) & IPROC_MSI_EQ_MASK;

		.....
		}

		
		 */
	} while (true);

What happens if two multi MSI cards are connected and continuously 
running traffic ? Will this handler ever come out? wont this stall CPU ?
Will the interrupts be routed to different CPU's in this case also?

Regards,
Valmiki


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus