[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87wo5fdjij.fsf@vitty.brq.redhat.com>
Date: Thu, 14 May 2020 10:10:28 +0200
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
Juergen Gross <jgross@...e.com>,
Stefano Stabellini <sstabellini@...nel.org>, x86@...nel.org
Subject: Re: [PATCH v2 0/3] x86/idt: Minor alloc_intr_gate() sanitization
Thomas Gleixner <tglx@...utronix.de> writes:
> Vitaly Kuznetsov <vkuznets@...hat.com> writes:
>> Vitaly Kuznetsov <vkuznets@...hat.com> 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. 'Hypervisor callback interrupts' on bare metal). Thomas
>>> suggested to expand this cosmetic change to making alloc_intr_gate()
>>> __init.
>>>
>>> Vitaly Kuznetsov (3):
>>> x86/xen: Split HVM vector callback setup and interrupt gate allocation
>>> x86/idt: Annotate alloc_intr_gate() with __init
>>> x86/idt: Keep spurious entries unset in system_vectors
>>>
>>
>> Ping?
>
> It's in my pile and I just did not come around to merge it.
>
No problem, just wanted to make sure it didn't slip through the
cracks. I see tip-bot already queued it, thanks!
--
Vitaly
Powered by blists - more mailing lists