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: <ec9cf2ed3f2db01fccf9a01e2739623297b3ca9d.camel@intel.com>
Date: Thu, 12 Jun 2025 02:20:51 +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 v2 06/18] KVM: x86: Move KVM_{GET,SET}_IRQCHIP ioctl
 helpers to irq.c

On Wed, 2025-06-11 at 14:35 -0700, Sean Christopherson wrote:
> Move the ioctl helpers for getting/setting fully in-kernel IRQ chip state
> to irq.c, partly to trim down x86.c, but mostly in preparation for adding
> a Kconfig to control support for in-kernel I/O APIC, PIC, and PIT
> emulation.
> 
> No functional change intended.
> 
> Signed-off-by: Sean Christopherson <seanjc@...gle.com>
> ---

Acked-by: Kai Huang <kai.huang@...el.com>

[...]

> --- a/arch/x86/kvm/irq.h
> +++ b/arch/x86/kvm/irq.h
> @@ -66,6 +66,9 @@ void kvm_pic_update_irq(struct kvm_pic *s);
>  int kvm_pic_set_irq(struct kvm_kernel_irq_routing_entry *e, struct kvm *kvm,
>  		    int irq_source_id, int level, bool line_status);
>  
> +int kvm_vm_ioctl_get_irqchip(struct kvm *kvm, struct kvm_irqchip *chip);
> +int kvm_vm_ioctl_set_irqchip(struct kvm *kvm, struct kvm_irqchip *chip);
> +

I think we need to include <uapi/linux/kvm.h> for 'struct kvm_irqchip', just
like you did for "i8254.h" in previous patch?

I checked the "irq.h" and it doesn't seem to be obvious that we don't need
it.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ