Received-SPF: pass (google.com: domain of linux-kernel+bounces-97956-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Precedence: bulk
MIME-Version: 1.0
References: <20240223211547.3348606-1-seanjc@google.com> <ZdkO0bgL40l10YnU@google.com>
In-Reply-To: <ZdkO0bgL40l10YnU@google.com>
From: Paolo Bonzini <pbonzini@redhat.com>
Date: Sat, 9 Mar 2024 17:30:26 +0100
Message-ID: <CABgObfbvJ=9hc0sxzgW4fXebn66wy4LoKdKg7HWc9t1mihBjAg@mail.gmail.com>
Subject: Re: [GIT PULL] KVM: GUEST_MEMFD fixes for 6.8
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 23, 2024 at 10:32=E2=80=AFPM Sean Christopherson <seanjc@google=
com> wrote:
>
> On Fri, Feb 23, 2024, Sean Christopherson wrote:
> > Minor fixes related GUEST_MEMFD.  I _just_ posted these, and they've on=
ly
> > been in -next for one night, but I am sending this now to ensure you se=
e it
> > asap, as patch 1 in particular affects KVM's ABI, i.e. really should la=
nd
> > in 6.8 before GUEST_MEMFD support is officially released.
> >
> > The following changes since commit c48617fbbe831d4c80fe84056033f17b70a3=
1136:
> >
> >   Merge tag 'kvmarm-fixes-6.8-3' of git://git.kernel.org/pub/scm/linux/=
kernel/git/kvmarm/kvmarm into HEAD (2024-02-21 05:18:56 -0500)
> >
> > are available in the Git repository at:
> >
> >   https://github.com/kvm-x86/linux.git tags/kvm-x86-guest_memfd_fixes-6=
8
> >
> > for you to fetch changes up to 2dfd2383034421101300a3b7325cf339a182d218=
:
> >
> >   KVM: selftests: Add a testcase to verify GUEST_MEMFD and READONLY are=
 exclusive (2024-02-22 17:07:06 -0800)
> >
> > ----------------------------------------------------------------
> > KVM GUEST_MEMFD fixes for 6.8:
> >
> >  - Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_READONLY to
> >    avoid creating ABI that KVM can't sanely support.
> >
> >  - Update documentation for KVM_SW_PROTECTED_VM to make it abundantly
> >    clear that such VMs are purely a development and testing vehicle, an=
d
> >    come with zero guarantees.
> >
> >  - Limit KVM_SW_PROTECTED_VM guests to the TDP MMU, as the long term pl=
an
> >    is to support confidential VMs with deterministic private memory (SN=
P
> >    and TDX) only in the TDP MMU.
> >
> >  - Fix a bug in a GUEST_MEMFD negative test that resulted in false pass=
es
> >    when verifying that KVM_MEM_GUEST_MEMFD memslots can't be dirty logg=
ed.
> >
> > ----------------------------------------------------------------
> > Sean Christopherson (5):
> >       KVM: Make KVM_MEM_GUEST_MEMFD mutually exclusive with KVM_MEM_REA=
DONLY
>
> Almost forgot, just as an FYI, this has a minor conflict with your kvm/kv=
m-uapi
> branch.  I've been fixing it up in kvm-x86/next, and IIUC you don't feed =
kvm/master
> into -next, so I don't think Stephen will see a conflict?

I do feed it in linux-next, so he would, but it's not a big deal. I'll
pull it into kvm-next as well.

Paolo