linux-kernel - [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-next>] [day] [month] [year] [list]

Message-ID: <20230830000633.3158416-1-seanjc@google.com>
Date:   Tue, 29 Aug 2023 17:06:26 -0700
From:   Sean Christopherson <seanjc@...gle.com>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        Sean Christopherson <seanjc@...gle.com>
Subject: [GIT PULL] KVM: x86 pull requests for 6.6

Adding a cover letter of sorts this time around to try and make your life a bit
easier.  You should see a total of 7 pull requests:

  [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.