Received-SPF: pass (google.com: domain of linux-kernel+bounces-83769-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Tue, 27 Feb 2024 09:49:24 -0800
In-Reply-To: <Zd1cDyyx65J1IVK1@archie.me>
Precedence: bulk
Mime-Version: 1.0
References: <20240226190344.787149-1-pbonzini@redhat.com> <Zd1cDyyx65J1IVK1@archie.me>
Message-ID: <Zd4gpBsmTdXEZkWS@google.com>
Subject: Re: [PATCH v3 00/15] KVM: SEV: allow customizing VMSA features
From: Sean Christopherson <seanjc@google.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, 
	michael.roth@amd.com, aik@amd.com
Content-Type: text/plain; charset="us-ascii"

On Tue, Feb 27, 2024, Bagas Sanjaya wrote:
> On Mon, Feb 26, 2024 at 02:03:29PM -0500, Paolo Bonzini wrote:
> > v2->v3:
> > - use u64_to_user_addr()
> > - Compile sev.c if and only if CONFIG_KVM_AMD_SEV=y
> > - remove double signoffs
> > - rebase on top of kvm-x86/next
> 
> I can't apply this series on top of current kvm-x86/next. On what exact
> commit the series is based on?

Note that kvm-x86/next is my tree at https://github.com/kvm-x86/linux/tree/next.
Are you pulling that, or are you based off kvm/next (Paolo's tree at
git://git.kernel.org/pub/scm/virt/kvm/kvm.git)?

Because this series applies for me on all of these tags from kvm-x86.

  kvm-x86-next-2024.02.22
  kvm-x86-next-2024.02.23
  kvm-x86-next-2024.02.26
  kvm-x86-next-2024.02.26-2