[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <91444be8576ac220fb66cd8546697912988c4a87.camel@intel.com>
Date: Mon, 20 May 2024 19:02:23 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "Huang, Kai" <kai.huang@...el.com>, "Yamahata, Isaku"
<isaku.yamahata@...el.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"seanjc@...gle.com" <seanjc@...gle.com>, "sagis@...gle.com"
<sagis@...gle.com>, "isaku.yamahata@...ux.intel.com"
<isaku.yamahata@...ux.intel.com>, "isaku.yamahata@...il.com"
<isaku.yamahata@...il.com>, "Zhao, Yan Y" <yan.y.zhao@...el.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>, "dmatlack@...gle.com"
<dmatlack@...gle.com>, "pbonzini@...hat.com" <pbonzini@...hat.com>, "Aktas,
Erdem" <erdemaktas@...gle.com>
Subject: Re: [PATCH 10/16] KVM: x86/tdp_mmu: Support TDX private mapping for
TDP MMU
On Mon, 2024-05-20 at 11:58 -0700, Isaku Yamahata wrote:
> For hook names, we can use mirrored_private or reflect or handle?
> (or whatever better name)
>
> The current hook names
> {link, free}_private_spt(),
> {set, remove, zap}_private_spte()
>
> =>
> # use mirrored_private
> {link, free}_mirrored_private_spt(),
> {set, remove, zap}_mirrored_private_spte()
>
> or
> # use reflect (update or handle?) mirrored to private
> reflect_{linked, freeed}_mirrored_spt(),
> reflect_{set, removed, zapped}_mirrored_spte()
reflect is a nice name. I'm trying this path right now. I'll share a branch.
>
> or
> # Don't add anything. I think this would be confusing.
> {link, free}_spt(),
> {set, remove, zap}_spte()
Powered by blists - more mailing lists