[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABgObfbT_v23LbP7Mp-PfbnakHYrZ7+g3KfUA_BOnsp+7ivMYQ@mail.gmail.com>
Date: Mon, 3 Jun 2024 18:44:29 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Michael Roth <michael.roth@....com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Sean Christopherson <seanjc@...gle.com>, linux-coco@...ts.linux.dev, jroedel@...e.de,
thomas.lendacky@....com, vkuznets@...hat.com, pgonda@...gle.com,
rientjes@...gle.com, tobin@....com, bp@...en8.de, vbabka@...e.cz,
alpergun@...gle.com, ashish.kalra@....com, nikunj.dadhania@....com,
pankaj.gupta@....com, liam.merwick@...cle.com, papaluri@....com
Subject: Re: [PULL 00/19] KVM: Add AMD Secure Nested Paging (SEV-SNP)
Hypervisor Support
On Fri, May 31, 2024 at 5:23 AM Michael Roth <michael.roth@....com> wrote:
> As discussed during the PUCK call, here is a branch with fixup patches
> that incorporate the additional review/testing that came in after these
> patches were merged into kvm/next:
>
> https://github.com/mdroth/linux/commits/kvm-next-snp-fixes4/
>
> They are intended to be squashed in but can also be applied on top if
> that's preferable (but in that case the first 2 patches need to be
> squashed together to maintain build bisectability):
Yes, I'd rather not rebase kvm/next again so I applied them on top.
None of the issues are so egregiously bad.
Paolo
Powered by blists - more mailing lists