linux-kernel - Re: [RFC 1/4]x86: cleanup vector usage

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:	Sat, 06 Nov 2010 13:45:34 +0800
From:	Shaohua Li <shaohua.li@...el.com>
To:	Cyrill Gorcunov <gorcunov@...il.com>
Cc:	lkml <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Andi Kleen <andi@...stfloor.org>,
	"hpa@...or.com" <hpa@...or.com>
Subject: Re: [RFC 1/4]x86: cleanup vector usage

On Sat, 2010-11-06 at 04:55 +0800, Cyrill Gorcunov wrote:
> On Wed, Nov 03, 2010 at 02:44:18PM +0800, Shaohua Li wrote:
> > Cleanup the vector usage and make them continuous if possible.
> > 
> > Signed-off-by: Shaohua Li <shaohua.li@...el.com>
> > ---
> ...
> > -#define X86_PLATFORM_IPI_VECTOR		0xed
> > +#define X86_PLATFORM_IPI_VECTOR		0xf7
> >  
> >  /*
> >   * IRQ work vector:
> >   */
> > -#define IRQ_WORK_VECTOR			0xec
> > +#define IRQ_WORK_VECTOR			0xf6
> >  
> > -#define UV_BAU_MESSAGE			0xea
> > +#define UV_BAU_MESSAGE			0xf5
> >  
> >  /*
> >   * Self IPI vector for machine checks
> >   */
> > -#define MCE_SELF_VECTOR			0xeb
> > +#define MCE_SELF_VECTOR			0xf4
> >  
> >  /* Xen vector callback to receive events in a HVM domain */
> > -#define XEN_HVM_EVTCHN_CALLBACK		0xe9
> > +#define XEN_HVM_EVTCHN_CALLBACK		0xf3
> > +
> 
>  Hi Li, this is not just a cleanup -- irq priority were changed as
> well, but I suppose it's harmless ;)
I didn't change the local apic timer vector because the comments say the
priority is important. For others, I do suppose it's harmless.

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