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
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
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
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
4 matches
Mail list logo