[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240416235949.GC3039520@ls.amr.corp.intel.com>
Date: Tue, 16 Apr 2024 16:59:49 -0700
From: Isaku Yamahata <isaku.yamahata@...el.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
Cc: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"Yamahata, Isaku" <isaku.yamahata@...el.com>,
"seanjc@...gle.com" <seanjc@...gle.com>,
"Huang, Kai" <kai.huang@...el.com>,
"federico.parola@...ito.it" <federico.parola@...ito.it>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"isaku.yamahata@...il.com" <isaku.yamahata@...il.com>,
"dmatlack@...gle.com" <dmatlack@...gle.com>,
"michael.roth@....com" <michael.roth@....com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
isaku.yamahata@...ux.intel.com
Subject: Re: [PATCH v2 04/10] KVM: x86/mmu: Make __kvm_mmu_do_page_fault()
return mapped level
On Tue, Apr 16, 2024 at 02:40:39PM +0000,
"Edgecombe, Rick P" <rick.p.edgecombe@...el.com> wrote:
> On Wed, 2024-04-10 at 15:07 -0700, isaku.yamahata@...el.com wrote:
> > From: Isaku Yamahata <isaku.yamahata@...el.com>
> >
> > The guest memory population logic will need to know what page size or level
> > (4K, 2M, ...) is mapped.
>
> TDX needs this, but do the normal VM users need to have it fixed to 4k? Is it
> actually good?
I meant that the function, kvm_arch_vcpu_map_memory(), in
[PATCH v2 06/10] KVM: x86: Implement kvm_arch_vcpu_map_memory() needs level.
No logic in this patch series enforces to fixed 4K.
gmem_max_level() hook will determine it.
https://lore.kernel.org/all/20240404185034.3184582-12-pbonzini@redhat.com/
I'll update the commit message to reflect it.
--
Isaku Yamahata <isaku.yamahata@...el.com>
Powered by blists - more mailing lists