[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <af89758d-d029-419e-bcb5-713b2460163d@intel.com>
Date: Mon, 6 Jan 2025 18:51:13 +0800
From: Xiaoyao Li <xiaoyao.li@...el.com>
To: Binbin Wu <binbin.wu@...ux.intel.com>, pbonzini@...hat.com,
seanjc@...gle.com, kvm@...r.kernel.org
Cc: rick.p.edgecombe@...el.com, kai.huang@...el.com, adrian.hunter@...el.com,
reinette.chatre@...el.com, tony.lindgren@...ux.intel.com,
isaku.yamahata@...el.com, yan.y.zhao@...el.com, chao.gao@...el.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/16] KVM: TDX: TDX interrupts
On 12/9/2024 9:07 AM, Binbin Wu wrote:
> Hi,
>
> This patch series introduces the support of interrupt handling for TDX
> guests, including virtual interrupt injection and VM-Exits caused by
> vectored events.
>
(I'm not sure if it is the correct place to raise the discussion on
KVM_SET_LAPIC and KVM_SET_LAPIC for TDX. But it seems the most related
series)
Should KVM reject KVM_GET_LAPIC and KVM_SET_LAPIC for TDX?
Powered by blists - more mailing lists