linux-kernel - Re: [GIT PULL] KVM: x86 pull requests for 6.6

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABgObfYxjEiHARA2yCep7ck5snVYC1Ckh9prp3Y8J9xyRea8cw@mail.gmail.com>
Date:   Thu, 31 Aug 2023 19:30:35 +0200
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Sean Christopherson <seanjc@...gle.com>
Cc:     kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] KVM: x86 pull requests for 6.6

On Wed, Aug 30, 2023 at 2:06 AM Sean Christopherson <seanjc@...gle.com> wrote:
>
> Adding a cover letter of sorts this time around to try and make your life a bit
> easier.

Appreciated, but not particularly necessary. :)

If anything, I would prefer to have pull requests during the
development period if any larger features become ready, so that
conflicts become apparent earlier. Not a huge deal, we can sort out
the specifics when we meet at Plumbers.

Paolo

>   [GIT PULL] KVM: Non-x86 changes for 6.6
>   [GIT PULL] KVM: x86: Misc changes for 6.6
>   [GIT PULL] KVM: x86: MMU changes for 6.6
>   [GIT PULL] KVM: x86: PMU changes for 6.6
>   [GIT PULL] KVM: x86: Selftests changes for 6.6
>   [GIT PULL] KVM: x86: SVM changes for 6.6
>   [GIT PULL] KVM: x86: VMX changes for 6.6
>
> There is a trivial conflict between "Non-x86" and "MMU", and a less trivial one
> between "Misc" and "SVM".  FWIW, I recommend pulling "Misc" after "SVM", I found
> the conflict that's generated by merging "Misc" before "SVM" to be terribly
> confusing.  Details in the "Non-x86" and "Misc" requests respectively.