On Mon, Apr 01, 2024 at 01:06:07PM +0800, Binbin Wu <binbin.wu@xxxxxxxxxxxxxxx> wrote: > > > On 3/30/2024 5:24 AM, Michael Roth wrote: > > It has been reported that the internal workings of > > kvm_gmem_prepare_folio() incurs noticeable overhead for large guests > > even for platforms where kvm_arch_gmem_prepare() is a no-op. > > > > Provide a new kvm_arch_gmem_prepare_needed() hook so that architectures > > that set CONFIG_HAVE_KVM_GMEM_PREPARE can still opt-out of issuing the > > kvm_arch_gmem_prepare() callback > > Just wondering which part has big impact on performance, > the issue of kvm_arch_gmem_prepare() callback or the preparation code for > the kvm_arch_gmem_prepare()? I'm fine without this patch for now baecause this is optimization. -- Isaku Yamahata <isaku.yamahata@xxxxxxxxx>
