From: Paul Mackerras <paulus@ozlabs.org> To: "Paolo Bonzini" <pbonzini@redhat.com>, "Radim Krčmář" <rkrcmar@redhat.com>, kvm@vger.kernel.org Cc: kvm-ppc@vger.kernel.org Subject: [GIT PULL] Please pull my kvm-ppc-fixes-5.2-1 tag Date: Thu, 30 May 2019 21:59:44 +1000 [thread overview] Message-ID: <20190530115944.GA6675@blackberry> (raw) Paolo or Radim, Please do a pull from my kvm-ppc-fixes-5.2-1 tag to get a series of commits which should go into 5.2 (i.e. via the master branch of the kvm tree). They are mostly fixes for the new code which allows guests to access the XIVE interrupt controller on POWER9 machines directly, and locking fixes to solve host deadlock issues. It turns out that the PPC KVM code had been using the kvm->lock mutex in several places where the vcpu mutex was already held. Although this is contrary to what Documentation/virtual/kvm/locking.txt says, lockdep didn't complain about it in the past because we (apparently) had no places where a vcpu mutex was taken with kvm->lock held. Now there is such a place, in the recently-added XIVE code. Thus we now need to fix those other places that take the locks in the wrong order. Thanks, Paul. The following changes since commit cd6c84d8f0cdc911df435bb075ba22ce3c605b07: Linux 5.2-rc2 (2019-05-26 16:49:19 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-fixes-5.2-1 for you to fetch changes up to d724c9e54939a597592de3659541da11fc7aa112: KVM: PPC: Book3S HV: Restore SPRG3 in kvmhv_p9_guest_entry() (2019-05-30 14:00:54 +1000) ---------------------------------------------------------------- PPC KVM fixes for 5.2 - Several bug fixes for the new XIVE-native code. - Replace kvm->lock by other mutexes in several places where we hold a vcpu mutex, to avoid lock order inversions. - Fix a lockdep warning on guest entry for radix-mode guests. - Fix a bug causing user-visible corruption of SPRG3 on the host. ---------------------------------------------------------------- Cédric Le Goater (7): KVM: PPC: Book3S HV: XIVE: Clear file mapping when device is released KVM: PPC: Book3S HV: XIVE: Do not test the EQ flag validity when resetting KVM: PPC: Book3S HV: XIVE: Fix the enforced limit on the vCPU identifier KVM: PPC: Book3S HV: XIVE: Introduce a new mutex for the XIVE device KVM: PPC: Book3S HV: XIVE: Do not clear IRQ data of passthrough interrupts KVM: PPC: Book3S HV: XIVE: Take the srcu read lock when accessing memslots KVM: PPC: Book3S HV: XIVE: Fix page offset when clearing ESB pages Paul Mackerras (5): KVM: PPC: Book3S HV: Avoid touching arch.mmu_ready in XIVE release functions KVM: PPC: Book3S HV: Use new mutex to synchronize MMU setup KVM: PPC: Book3S: Use new mutex to synchronize access to rtas token list KVM: PPC: Book3S HV: Don't take kvm->lock around kvm_for_each_vcpu KVM: PPC: Book3S HV: Fix lockdep warning when entering guest on POWER9 Suraj Jitindar Singh (1): KVM: PPC: Book3S HV: Restore SPRG3 in kvmhv_p9_guest_entry() arch/powerpc/include/asm/kvm_host.h | 2 + arch/powerpc/kvm/book3s.c | 1 + arch/powerpc/kvm/book3s_64_mmu_hv.c | 36 ++++++------ arch/powerpc/kvm/book3s_hv.c | 48 ++++++++++------ arch/powerpc/kvm/book3s_rtas.c | 14 ++--- arch/powerpc/kvm/book3s_xive.c | 55 +++++++++---------- arch/powerpc/kvm/book3s_xive.h | 1 + arch/powerpc/kvm/book3s_xive_native.c | 100 +++++++++++++++++++--------------- 8 files changed, 142 insertions(+), 115 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mackerras <paulus@ozlabs.org> To: "Paolo Bonzini" <pbonzini@redhat.com>, "Radim Krčmář" <rkrcmar@redhat.com>, kvm@vger.kernel.org Cc: kvm-ppc@vger.kernel.org Subject: [GIT PULL] Please pull my kvm-ppc-fixes-5.2-1 tag Date: Thu, 30 May 2019 11:59:44 +0000 [thread overview] Message-ID: <20190530115944.GA6675@blackberry> (raw) In-Reply-To: <20180303091717.GA14569@fergus.ozlabs.ibm.com> Paolo or Radim, Please do a pull from my kvm-ppc-fixes-5.2-1 tag to get a series of commits which should go into 5.2 (i.e. via the master branch of the kvm tree). They are mostly fixes for the new code which allows guests to access the XIVE interrupt controller on POWER9 machines directly, and locking fixes to solve host deadlock issues. It turns out that the PPC KVM code had been using the kvm->lock mutex in several places where the vcpu mutex was already held. Although this is contrary to what Documentation/virtual/kvm/locking.txt says, lockdep didn't complain about it in the past because we (apparently) had no places where a vcpu mutex was taken with kvm->lock held. Now there is such a place, in the recently-added XIVE code. Thus we now need to fix those other places that take the locks in the wrong order. Thanks, Paul. The following changes since commit cd6c84d8f0cdc911df435bb075ba22ce3c605b07: Linux 5.2-rc2 (2019-05-26 16:49:19 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-fixes-5.2-1 for you to fetch changes up to d724c9e54939a597592de3659541da11fc7aa112: KVM: PPC: Book3S HV: Restore SPRG3 in kvmhv_p9_guest_entry() (2019-05-30 14:00:54 +1000) ---------------------------------------------------------------- PPC KVM fixes for 5.2 - Several bug fixes for the new XIVE-native code. - Replace kvm->lock by other mutexes in several places where we hold a vcpu mutex, to avoid lock order inversions. - Fix a lockdep warning on guest entry for radix-mode guests. - Fix a bug causing user-visible corruption of SPRG3 on the host. ---------------------------------------------------------------- Cédric Le Goater (7): KVM: PPC: Book3S HV: XIVE: Clear file mapping when device is released KVM: PPC: Book3S HV: XIVE: Do not test the EQ flag validity when resetting KVM: PPC: Book3S HV: XIVE: Fix the enforced limit on the vCPU identifier KVM: PPC: Book3S HV: XIVE: Introduce a new mutex for the XIVE device KVM: PPC: Book3S HV: XIVE: Do not clear IRQ data of passthrough interrupts KVM: PPC: Book3S HV: XIVE: Take the srcu read lock when accessing memslots KVM: PPC: Book3S HV: XIVE: Fix page offset when clearing ESB pages Paul Mackerras (5): KVM: PPC: Book3S HV: Avoid touching arch.mmu_ready in XIVE release functions KVM: PPC: Book3S HV: Use new mutex to synchronize MMU setup KVM: PPC: Book3S: Use new mutex to synchronize access to rtas token list KVM: PPC: Book3S HV: Don't take kvm->lock around kvm_for_each_vcpu KVM: PPC: Book3S HV: Fix lockdep warning when entering guest on POWER9 Suraj Jitindar Singh (1): KVM: PPC: Book3S HV: Restore SPRG3 in kvmhv_p9_guest_entry() arch/powerpc/include/asm/kvm_host.h | 2 + arch/powerpc/kvm/book3s.c | 1 + arch/powerpc/kvm/book3s_64_mmu_hv.c | 36 ++++++------ arch/powerpc/kvm/book3s_hv.c | 48 ++++++++++------ arch/powerpc/kvm/book3s_rtas.c | 14 ++--- arch/powerpc/kvm/book3s_xive.c | 55 +++++++++---------- arch/powerpc/kvm/book3s_xive.h | 1 + arch/powerpc/kvm/book3s_xive_native.c | 100 +++++++++++++++++++--------------- 8 files changed, 142 insertions(+), 115 deletions(-)
next reply other threads:[~2019-05-30 12:00 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-30 11:59 Paul Mackerras [this message] 2019-05-30 11:59 ` [GIT PULL] Please pull my kvm-ppc-fixes-5.2-1 tag Paul Mackerras 2019-05-31 22:48 ` Paolo Bonzini 2019-05-31 22:48 ` Paolo Bonzini -- strict thread matches above, loose matches on Subject: below -- 2020-04-20 23:53 [GIT PULL] Please pull my kvm-ppc-fixes-5.7-1 tag Paul Mackerras 2020-04-20 23:53 ` Paul Mackerras 2020-04-21 13:37 ` Paolo Bonzini 2020-04-21 13:37 ` Paolo Bonzini 2019-12-19 0:19 [GIT PULL] Please pull my kvm-ppc-fixes-5.5-1 tag Paul Mackerras 2019-12-19 0:19 ` Paul Mackerras 2019-12-22 12:18 ` Paolo Bonzini 2019-12-22 12:18 ` Paolo Bonzini 2019-10-21 4:19 [GIT PULL] Please pull my kvm-ppc-fixes-5.4-1 tag Paul Mackerras 2019-10-21 4:19 ` Paul Mackerras 2019-10-22 11:12 ` Paolo Bonzini 2019-10-22 11:12 ` Paolo Bonzini 2019-08-27 9:53 [GIT PULL] Please pull my kvm-ppc-fixes-5.3-1 tag Paul Mackerras 2019-08-27 9:53 ` Paul Mackerras 2019-08-27 15:49 ` Radim Krčmář 2019-08-27 15:49 ` Radim Krčmář 2019-04-07 22:12 [GIT PULL] Please pull my kvm-ppc-fixes-5.1-1 tag Paul Mackerras 2019-04-07 22:12 ` Paul Mackerras 2019-04-18 4:05 ` Paul Mackerras 2019-04-18 4:05 ` Paul Mackerras 2019-04-18 16:53 ` Paolo Bonzini 2019-04-18 16:53 ` Paolo Bonzini 2018-03-03 9:17 [GIT PULL] Please pull my kvm-ppc-fixes-4.16-1 tag Paul Mackerras 2018-03-06 17:08 ` Radim Krčmář 2018-03-14 8:57 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.16-2 tag Paul Mackerras 2018-03-15 20:57 ` Paolo Bonzini 2018-03-23 4:46 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.16-3 tag Paul Mackerras 2018-03-23 17:21 ` Paolo Bonzini 2018-05-24 5:34 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.17-1 tag Paul Mackerras 2018-05-24 17:02 ` Radim Krčmář 2018-08-22 12:08 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-1 tag Paul Mackerras 2018-09-14 9:57 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-2 tag Paul Mackerras 2018-09-18 13:22 ` Paolo Bonzini 2018-10-05 0:29 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.19-3 tag Paul Mackerras 2018-10-05 7:43 ` Paolo Bonzini 2018-11-16 10:36 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.20-1 tag Paul Mackerras 2018-11-25 17:54 ` Paolo Bonzini
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190530115944.GA6675@blackberry \ --to=paulus@ozlabs.org \ --cc=kvm-ppc@vger.kernel.org \ --cc=kvm@vger.kernel.org \ --cc=pbonzini@redhat.com \ --cc=rkrcmar@redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.