linux-kernel - Re: [PATCH] x86/irq: Fix comment on IRQ vector layout

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

Message-ID: <5e231a57-a9c6-40c7-9115-5a809b104ff2@intel.com>
Date: Tue, 18 Jun 2024 14:11:56 -0700
From: Sohil Mehta <sohil.mehta@...el.com>
To: Jacob Pan <jacob.jun.pan@...ux.intel.com>
CC: <x86@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar
	<mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, Dave Hansen
	<dave.hansen@...ux.intel.com>, "H . Peter Anvin" <hpa@...or.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/irq: Fix comment on IRQ vector layout


>>   *  Vectors   0 ...  31 : system traps and exceptions - hardcoded events
>>   *  Vectors  32 ... 127 : device interrupts
>>   *  Vector  128         : legacy int80 syscall interface
>> - *  Vectors 129 ... LOCAL_TIMER_VECTOR-1
>> - *  Vectors LOCAL_TIMER_VECTOR ... 255 : special interrupts
>> + *  Vectors 129 ... FIRST_SYSTEM_VECTOR-1
> Should this range be explicitly labeled as "device interrupts"?
> 

I thought about that as well. I wasn't sure why it was left out in the
first place.

Will change it in the next version unless someone suggests otherwise.

-Sohil