linux-kernel - [PATCH] x86_64 irq: reuse vector for set_xxx_irq

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

Message-ID: <86802c440610230002x340e3f95pa8ee98caa02e7e@mail.gmail.com>
Date:	Mon, 23 Oct 2006 00:02:44 -0700
From:	"Yinghai Lu" <yinghai.lu@....com>
To:	"Andi Kleen" <ak@....de>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Muli Ben-Yehuda" <muli@...ibm.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Andrew Morton" <akpm@...l.org>, "Adrian Bunk" <bunk@...sta.de>
Subject: [PATCH] x86_64 irq: reuse vector for set_xxx_irq_affinity in phys flat mode

in phys flat mode, when using set_xxx_irq_affinity to irq balance from
one cpu to another,  _assign_irq_vector will get to increase last used
vector and get new vector. this will use up the vector if enough
set_xxx_irq_affintiy are called. and end with using same vector in
different cpu for different irq. (that is not what we want, we only
want to use same vector in different cpu for different irq when more
than 0x240 irq needed). To keep it simple, the vector should be resued
from one cpu to another instead of getting new vector.

Signed-off-by: Yinghai Lu <yinghai.lu@....com>

View attachment "io_apic_c_reuse_vector.diff" of type "text/x-patch" (1191 bytes)