[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4a2a75d2-05b5-4132-a3ea-fb2ec876b7c2@linux.intel.com>
Date: Wed, 19 Nov 2025 14:39:28 +0800
From: Binbin Wu <binbin.wu@...ux.intel.com>
To: Yan Zhao <yan.y.zhao@...el.com>
Cc: pbonzini@...hat.com, seanjc@...gle.com, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, x86@...nel.org, rick.p.edgecombe@...el.com,
dave.hansen@...el.com, kas@...nel.org, tabba@...gle.com,
ackerleytng@...gle.com, michael.roth@....com, david@...hat.com,
vannapurve@...gle.com, vbabka@...e.cz, thomas.lendacky@....com,
pgonda@...gle.com, fan.du@...el.com, jun.miao@...el.com,
ira.weiny@...el.com, isaku.yamahata@...el.com, xiaoyao.li@...el.com,
chao.p.peng@...el.com
Subject: Re: [RFC PATCH v2 14/23] KVM: TDX: Split and inhibit huge mappings if
a VMExit carries level info
On 11/19/2025 2:29 PM, Yan Zhao wrote:
[...]
>>> +static inline int tdx_check_accept_level(struct kvm_vcpu *vcpu, gfn_t gfn)
>> The function name sounds like it is just doing check, but it may split a
>> hugepage on mismatch.
>>
>> How about tdx_enforce_accept_level_mapping() or something else to reflect
>> the change could be make?
> What about tdx_honor_guest_accept_level()?
It looks good to me.
Powered by blists - more mailing lists