[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <447532e67e834f44c59beabe0bb2efba82644550.camel@intel.com>
Date: Wed, 27 Nov 2024 23:04:47 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "pbonzini@...hat.com" <pbonzini@...hat.com>, "Hansen, Dave"
<dave.hansen@...el.com>, "seanjc@...gle.com" <seanjc@...gle.com>
CC: "isaku.yamahata@...il.com" <isaku.yamahata@...il.com>,
"yuan.yao@...el.com" <yuan.yao@...el.com>, "x86@...nel.org" <x86@...nel.org>,
"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>, "Zhao, Yan Y" <yan.y.zhao@...el.com>,
"tony.lindgren@...ux.intel.com" <tony.lindgren@...ux.intel.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>, "Hunter, Adrian"
<adrian.hunter@...el.com>, "Yamahata, Isaku" <isaku.yamahata@...el.com>,
"Huang, Kai" <kai.huang@...el.com>
Subject: Re: [RFC PATCH 1/6] x86/virt/tdx: Add SEAMCALL wrappers for TDX KeyID
management
On Wed, 2024-11-27 at 19:15 +0100, Paolo Bonzini wrote:
> > What if we just move these members from hpa_t to pfn_t? It keeps us off
> > struct
> > page, but addresses some of Dave's concerns about hpa_t looking like a
> > specific
> > address.
>
> For tdr I agree with Dave that you probably want a struct which stores
> the struct page*. Currently the code is using __get_free_page(), but
> it's a small change to have it use alloc_page() instead, and
> __free_page() instead of free_page().
>
> The only difference on the arch/x86/virt/ side is a bunch of added
> page_to_phys().
Thanks.
>
> Anyhow, whatever you post I'll take care of adjusting in the KVM patches.
I'm just throwing together a v2. We have the US holidays this week, so it may be
Monday.
Powered by blists - more mailing lists