[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d5c49c918a86d37995ed6388c1e77cd41fc51c19.camel@intel.com>
Date: Thu, 12 Sep 2024 14:43:03 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "seanjc@...gle.com" <seanjc@...gle.com>, "Huang, Kai"
<kai.huang@...el.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "pbonzini@...hat.com"
<pbonzini@...hat.com>, "nik.borisov@...e.com" <nik.borisov@...e.com>,
"dmatlack@...gle.com" <dmatlack@...gle.com>, "isaku.yamahata@...il.com"
<isaku.yamahata@...il.com>, "Zhao, Yan Y" <yan.y.zhao@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 05/21] KVM: VMX: Teach EPT violation helper about private
mem
On Thu, 2024-09-12 at 06:58 -0700, Sean Christopherson wrote:
> > Which clearly says it is checking the *faulting* GPA.
>
> I don't think that necessarily solves the problem either, because the reader
> has
> to know that the KVM looks at the shared bit.
>
> If open coding is undesirable
Yea, I think it's used in enough places that a helper is worth it.
> , maybe a very literal name, e.g. vmx_is_shared_bit_set()?
Sure, thanks.
Powered by blists - more mailing lists