linux-kernel - X86/irq: failed to assign vectors from CPU0

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: <0259E1C966E8C54AA93AA2B1240828E62C52C674@szxema507-mbs.china.huawei.com>
Date:	Thu, 26 Jun 2014 06:13:39 +0000
From:	"Zhangbo (Oscar)" <oscar.zhangbo@...wei.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	"Huangpeng (Peter)" <peter.huangpeng@...wei.com>,
	Yanxiaodan <yanxiaodan@...wei.com>,
	"Zhoujian (jay, Euler)" <jianjay.zhou@...wei.com>,
	Luonengjun <luonengjun@...wei.com>,
	"Huangweidong (C)" <weidong.huang@...wei.com>,
	Yanqiangjun <yanqiangjun@...wei.com>,
	"Zhaoyanbin (A)" <lefty.zhao@...wei.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	"Ingo Molnar" <mingo@...nel.org>,
	Alexander Gordeev <agordeev@...hat.com>,
	"Thomas Gleixner" <tglx@...utronix.de>
Subject: X86/irq: failed to assign vectors from CPU0

	Msi or Msi-x interrupts assign vectors from a CPU while the number of CUPs is more than 8. __assign_irq_vector() is responsible for assigning vectors from low-numbered CPUs by default. 
	If there are a lot of Msi or Msi-x interrupts, it will cause the low-numbered CPUs out of vectors, so the subsequent interrupts will be failed to allocate vectors from these CPUs. 
	What is the consideration of preferentially assigning vectors from low-numbered CPUs? How about assigning vectors from the CPUs which have the maximum number of unused vectors?
	Thank you in advance.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/