linux-kernel - Re: [PATCH v3] x86, irq: get correct available vectors for cpu disable

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]

Date:	Wed, 26 Mar 2014 10:04:52 -0700
From:	Yinghai Lu <yinghai@...nel.org>
To:	Linn Crosetto <linn@...com>
Cc:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Prarit Bhargava <prarit@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] x86, irq: get correct available vectors for cpu disable

On Wed, Mar 26, 2014 at 9:50 AM, Linn Crosetto <linn@...com> wrote:
> On Tue, Mar 25, 2014 at 05:18:53PM -0700, Yinghai Lu wrote:
>
> Just noting that not all bits above first_system_vector are set in the bitmap,
> so the comment in asm/desc.h and the change log could be misleading:
>
> /* used_vectors is BITMAP for irq is not managed by percpu vector_irq */
>

Do you mean some vector that is neither used by percpu_vector_irq nor
system_vector
after first_system_vector ?

Anyway if bit is set in used_vectors, that vector can not be used by
percpu vector_irq.

so that statement looks still right.

Feel free to suggest right comment or changelog.

> I have tested and the patch itself is good.

Good.

Thanks

Yinghai
--
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/