linux-kernel - Re: [PATCH 11/15] KVM: x86: Add CONFIG_KVM_IOAPIC to allow disabling in-kernel I/O APIC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <019c1023c26e827dc538f24d885ec9a8530ad4af.camel@intel.com>
Date: Thu, 29 May 2025 11:57:02 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "pbonzini@...hat.com" <pbonzini@...hat.com>, "seanjc@...gle.com"
	<seanjc@...gle.com>, "vkuznets@...hat.com" <vkuznets@...hat.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 11/15] KVM: x86: Add CONFIG_KVM_IOAPIC to allow disabling
 in-kernel I/O APIC

On Thu, 2025-05-29 at 23:55 +1200, Kai Huang wrote:
> On Mon, 2025-05-19 at 16:28 -0700, Sean Christopherson wrote:
> > Add a Kconfig to allowing building KVM without support for emulating an
> 		   ^
> 		   allow
> 
> > I/O APIC, PIC, and PIT, which is desirable for deployments that effectively
> > don't support a fully in-kernel IRQ chip, i.e. never expect any VMM to
> > create an in-kernel I/O APIC.  
> > 
> 
> Do you happen to know what developments don't support a full in-kernel IRQ chip?
> 
> Do they only support userspace IRQ chip, or not support any IRQ chip at all?

Forgot to ask:

Since this new Kconfig option is not only for IOAPIC but also includes PIC and
PIT, is CONFIG_KVM_IRQCHIP a better name?