Re: [PATCH] x86/apic: Initialize TPR to block interrupts 16-31

2019-07-15 Thread Andrew Cooper
On 14/07/2019 18:21, Nadav Amit wrote: >> On Jul 14, 2019, at 8:23 AM, Andy Lutomirski wrote: >> >> The APIC, per spec, is fundamentally confused and thinks that >> interrupt vectors 16-31 are valid. This makes no sense -- the CPU >> reserves vectors 0-31 for exceptions (faults, traps, etc). >>

Re: [PATCH] x86/apic: Initialize TPR to block interrupts 16-31

2019-07-14 Thread Nadav Amit
> On Jul 14, 2019, at 8:23 AM, Andy Lutomirski wrote: > > The APIC, per spec, is fundamentally confused and thinks that > interrupt vectors 16-31 are valid. This makes no sense -- the CPU > reserves vectors 0-31 for exceptions (faults, traps, etc). > Obviously, no device should actually produce

[PATCH] x86/apic: Initialize TPR to block interrupts 16-31

2019-07-14 Thread Andy Lutomirski
The APIC, per spec, is fundamentally confused and thinks that interrupt vectors 16-31 are valid. This makes no sense -- the CPU reserves vectors 0-31 for exceptions (faults, traps, etc). Obviously, no device should actually produce an interrupt with vector 16-31, but we can improve robustness by