[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aWmEegVP_A613WIr@google.com>
Date: Thu, 15 Jan 2026 16:21:14 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Yan Zhao <yan.y.zhao@...el.com>
Cc: pbonzini@...hat.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@...nel.org, vannapurve@...gle.com,
sagis@...gle.com, vbabka@...e.cz, thomas.lendacky@....com,
nik.borisov@...e.com, pgonda@...gle.com, fan.du@...el.com, jun.miao@...el.com,
francescolavra.fl@...il.com, jgross@...e.com, ira.weiny@...el.com,
isaku.yamahata@...el.com, xiaoyao.li@...el.com, kai.huang@...el.com,
binbin.wu@...ux.intel.com, chao.p.peng@...el.com, chao.gao@...el.com
Subject: Re: [PATCH v3 14/24] KVM: Change the return type of gfn_handler_t()
from bool to int
On Tue, Jan 06, 2026, Yan Zhao wrote:
> Modify the return type of gfn_handler_t() from bool to int. A negative
> return value indicates failure, while a return value of 1 signifies success
> with a flush required, and 0 denotes success without a flush required.
>
> This adjustment prepares for a later change that will enable
> kvm_pre_set_memory_attributes() to fail.
No, just don't support S-EPT hugepages with per-VM memory attributes. This type
of complexity isn't worth carrying for a feature we want to deprecate.
Powered by blists - more mailing lists