[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABgObfZoJjz1-CMGCQqNjA8i_DivgevEhw+EqfbD463JAMe_bA@mail.gmail.com>
Date: Thu, 31 Aug 2023 19:43:37 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Like Xu <like.xu.linux@...il.com>
Subject: Re: [GIT PULL] KVM: x86: MMU changes for 6.6
On Thu, Aug 31, 2023 at 7:27 PM Sean Christopherson <seanjc@...gle.com> wrote:
>
> +Like
>
> On Tue, Aug 29, 2023, Sean Christopherson wrote:
> > Please pull MMU changes for 6.6, with a healthy dose of KVMGT cleanups mixed in.
> > The other highlight is finally purging the old MMU_DEBUG code and replacing it
> > with CONFIG_KVM_PROVE_MMU.
> >
> > All KVMGT patches have been reviewed/acked and tested by KVMGT folks. A *huge*
> > thanks to them for all the reviews and testing, and to Yan in particular.
>
> FYI, Like found a brown paper bag bug[*] that causes selftests that move memory
> regions to fail when compiled with CONFIG_KVM_EXTERNAL_WRITE_TRACKING=y. I'm
> redoing testing today with that forced on, but barring more falling, the fix is:
Ok, I'll apply these by hand.
Paolo
Powered by blists - more mailing lists