Re: [PATCH v2 0/3] x86/idt: Minor alloc_intr_gate() sanitization

2020-05-14 Thread Vitaly Kuznetsov
Thomas Gleixner writes: > Vitaly Kuznetsov writes: >> Vitaly Kuznetsov writes: >> >>> This series is a successor of "[PATCH] x86/idt: Keep spurious entries unset >>> in system_vectors". >>> >>> The original issue I tried to address was that /proc/interrupts output >>> was always containing all

Re: [PATCH v2 0/3] x86/idt: Minor alloc_intr_gate() sanitization

2020-05-13 Thread Thomas Gleixner
Vitaly Kuznetsov writes: > Vitaly Kuznetsov writes: > >> This series is a successor of "[PATCH] x86/idt: Keep spurious entries unset >> in system_vectors". >> >> The original issue I tried to address was that /proc/interrupts output >> was always containing all possible system vectors, including

Re: [PATCH v2 0/3] x86/idt: Minor alloc_intr_gate() sanitization

2020-05-13 Thread Vitaly Kuznetsov
Vitaly Kuznetsov writes: > This series is a successor of "[PATCH] x86/idt: Keep spurious entries unset > in system_vectors". > > The original issue I tried to address was that /proc/interrupts output > was always containing all possible system vectors, including non allocated > ones (e.g. 'Hyperv

[PATCH v2 0/3] x86/idt: Minor alloc_intr_gate() sanitization

2020-04-28 Thread Vitaly Kuznetsov
This series is a successor of "[PATCH] x86/idt: Keep spurious entries unset in system_vectors". The original issue I tried to address was that /proc/interrupts output was always containing all possible system vectors, including non allocated ones (e.g. 'Hypervisor callback interrupts' on bare meta