[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0854fbf0-c885-4331-8e9d-30eaa557b266@intel.com>
Date: Wed, 4 Dec 2024 11:57:31 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Rick Edgecombe <rick.p.edgecombe@...el.com>, kvm@...r.kernel.org,
pbonzini@...hat.com, seanjc@...gle.com
Cc: isaku.yamahata@...il.com, kai.huang@...el.com,
linux-kernel@...r.kernel.org, tony.lindgren@...ux.intel.com,
xiaoyao.li@...el.com, yan.y.zhao@...el.com, x86@...nel.org,
adrian.hunter@...el.com, Isaku Yamahata <isaku.yamahata@...el.com>,
Binbin Wu <binbin.wu@...ux.intel.com>, Yuan Yao <yuan.yao@...el.com>
Subject: Re: [RFC PATCH v2 5/6] x86/virt/tdx: Add SEAMCALL wrappers for TDX
VM/vCPU field access
On 12/2/24 17:03, Rick Edgecombe wrote:
> +u64 tdh_vp_wr(struct tdx_vp *vp, u64 field, u64 data, u64 mask)
> +{
> + struct tdx_module_args args = {
> + .rcx = tdx_tdvpr_pa(vp),
> + .rdx = field,
> + .r8 = data,
> + .r9 = mask,
> + };
> +
> + return seamcall(TDH_VP_WR, &args);
> +}
> +EXPORT_SYMBOL_GPL(tdh_vp_wr);
There's a bit more tweaking you could _probably_ do here like giving
'field' a real type that means something, probably an enum. But that's
well into nitpicky territory and might not buy anything in practice.
Overall this set looks fine to me. The types are much more safe and
helpers are much more self-explanatory. So, for the series:
Acked-by: Dave Hansen <dave.hansen@...ux.intel.com>
Powered by blists - more mailing lists