Messages in this thread | ![/](/images/icornerl.gif) | | Subject | Re: [RFC 1/4]x86: cleanup vector usage | From | Shaohua Li <> | Date | Sat, 06 Nov 2010 13:45:34 +0800 |
| |
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@intel.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.
| ![\](/images/icornerr.gif) |