[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85a8bebd3c92292472bd50c6a03d85365c4979b1.camel@intel.com>
Date: Fri, 17 Jan 2025 10:46:24 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "seanjc@...gle.com" <seanjc@...gle.com>
CC: "Gao, Chao" <chao.gao@...el.com>, "Edgecombe, Rick P"
<rick.p.edgecombe@...el.com>, "binbin.wu@...ux.intel.com"
<binbin.wu@...ux.intel.com>, "Li, Xiaoyao" <xiaoyao.li@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Hunter,
Adrian" <adrian.hunter@...el.com>, "Chatre, Reinette"
<reinette.chatre@...el.com>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"Zhao, Yan Y" <yan.y.zhao@...el.com>, "tony.lindgren@...ux.intel.com"
<tony.lindgren@...ux.intel.com>, "pbonzini@...hat.com" <pbonzini@...hat.com>,
"Yamahata, Isaku" <isaku.yamahata@...el.com>
Subject: Re: [PATCH 12/16] KVM: TDX: Inhibit APICv for TDX guest
On Fri, 2025-01-17 at 09:53 +0000, Huang, Kai wrote:
> Btw, IIUC, in case of IRQCHIP split, KVM uses KVM_IRQ_ROUTING_MSI for routes of
> GSIs. But it seems KVM only allows level-triggered MSI to be signaled (which is
> a surprising):
>
> int kvm_set_msi(struct kvm_kernel_irq_routing_entry *e,
> struct kvm *kvm, int irq_source_id, int level, bool line_status)
> {
> struct kvm_lapic_irq irq;
>
> if (kvm_msi_route_invalid(kvm, e))
> return -EINVAL;
>
> if (!level)
> return -1;
>
> kvm_set_msi_irq(kvm, e, &irq);
>
> return kvm_irq_delivery_to_apic(kvm, NULL, &irq, NULL);
> }
Ah sorry this 'level' is not trig_mode. Please ignore :-)
Powered by blists - more mailing lists