[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZAdgVrkKKUNyLe8M@google.com>
Date: Tue, 7 Mar 2023 08:03:34 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: David Stevens <stevensd@...omium.org>
Cc: David Woodhouse <dwmw@...zon.co.uk>, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] KVM: x86: replace kvm_vcpu_map usage in vmx
On Mon, Mar 06, 2023, David Stevens wrote:
> On Sat, Jan 28, 2023 at 4:19 AM Sean Christopherson <seanjc@...gle.com> wrote:
> >
> > On Fri, Jan 27, 2023, David Stevens wrote:
> > > From: David Stevens <stevensd@...omium.org>
> > >
> > > This series replaces the usage of kvm_vcpu_map in vmx with
> > > gfn_to_pfn_cache. See [1] for details on why kvm_vcpu_map is broken.
> > >
> > > The presence of kvm_vcpu_map blocks another series I would like to
> > > try to merge [2]. Although I'm not familiar with the internals of vmx,
> > > I've gone ahead and taken a stab at this cleanup. I've done some manual
> > > testing with nested VMs, and KVM selftests pass, but thorough feedback
> > > would be appreciated. Once this cleanup is done, I'll take a look at
> > > removing kvm_vcpu_map from svm.
> >
> > Woot, been waiting for someone to take this one, thanks! It'll likely be a week
> > or two until I get 'round to this, but it's definitely something I want to get
> > merged sooner than later.
>
> Sean, will you be able to get to this in the next few weeks?
Yes, so long as your definition of "few" means 2-4 ;-)
Powered by blists - more mailing lists