[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <603be51644f179d0f9ece1cd35e8a744ffe21b6f.camel@intel.com>
Date: Tue, 14 Jan 2025 22:27:59 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "pbonzini@...hat.com"
<pbonzini@...hat.com>, "seanjc@...gle.com" <seanjc@...gle.com>, "Zhao, Yan Y"
<yan.y.zhao@...el.com>
CC: "Huang, Kai" <kai.huang@...el.com>, "binbin.wu@...ux.intel.com"
<binbin.wu@...ux.intel.com>, "Li, Xiaoyao" <xiaoyao.li@...el.com>, "Lindgren,
Tony" <tony.lindgren@...el.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "Chatre, Reinette"
<reinette.chatre@...el.com>, "dmatlack@...gle.com" <dmatlack@...gle.com>,
"Hunter, Adrian" <adrian.hunter@...el.com>, "Yamahata, Isaku"
<isaku.yamahata@...el.com>, "isaku.yamahata@...il.com"
<isaku.yamahata@...il.com>
Subject: Re: [PATCH 0/7] KVM: TDX SEPT SEAMCALL retry
We should probably...
On Mon, 2025-01-13 at 10:09 +0800, Yan Zhao wrote:
> KVM: TDX: Return -EBUSY when tdh_mem_page_add() encounters
> TDX_OPERAND_BUSY
Squash this in "KVM: TDX: Add an ioctl to create initial guest
memory" in kvm-coco-queue.
> KVM: x86/mmu: Return RET_PF* instead of 1 in kvm_mmu_page_fault()
Recommend this to go through kvm/x86 tree separately?
> KVM: TDX: Retry locally in TDX EPT violation handler on RET_PF_RETRY
> KVM: TDX: Kick off vCPUs when SEAMCALL is busy during TD page removal
Include these in kvm-coco-queue and drop "x86/virt/tdx: Retry seamcall when
TDX_OPERAND_BUSY with operand SEPT"
> fixup! KVM: TDX: Implement hooks to propagate changes of TDP MMU
> mirror page table
> fixup! KVM: TDX: Implement hooks to propagate changes of TDP MMU
> mirror page table
Squash these into kvm-coco-queue.
> fixup! KVM: TDX: Implement TDX vcpu enter/exit path
Add this in the next version of "TDX vcpu enter/exit path".
How does that sound?
Powered by blists - more mailing lists