[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240226174830.GA177224@ls.amr.corp.intel.com>
Date: Mon, 26 Feb 2024 09:48:30 -0800
From: Isaku Yamahata <isaku.yamahata@...ux.intel.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: Sean Christopherson <seanjc@...gle.com>, isaku.yamahata@...el.com,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
isaku.yamahata@...il.com, erdemaktas@...gle.com,
Sagi Shahar <sagis@...gle.com>, Kai Huang <kai.huang@...el.com>,
chen.bo@...el.com, hang.yuan@...el.com, tina.zhang@...el.com,
isaku.yamahata@...ux.intel.com
Subject: Re: [PATCH v18 032/121] KVM: x86/mmu: introduce config for PRIVATE
KVM MMU
On Tue, Feb 13, 2024 at 05:47:43PM +0100,
Paolo Bonzini <pbonzini@...hat.com> wrote:
> On Tue, Feb 13, 2024 at 3:57 AM Sean Christopherson <seanjc@...gle.com> wrote:
> > The only thing that even so much as approaches being a hot path is
> > kvm_gfn_shared_mask(), and if that needs to be optimized, then we'd probably be
> > better off with a static_key, a la kvm_has_noapic_vcpu (though I'm *extremely*
> > skeptical that that adds any measurable benefit).
>
> I'm okay with killing it altogether.
I eliminated this config.
--
Isaku Yamahata <isaku.yamahata@...ux.intel.com>
Powered by blists - more mailing lists