All of lore.kernel.org
 help / color / mirror / Atom feed
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, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-5.4-1 tag
Date: Fri, 06 Sep 2019 12:04:15 +0000	[thread overview]
Message-ID: <20190906120415.GA1625@blackberry> (raw)
In-Reply-To: <20190828232353.GA4485@blackberry>

On Thu, Aug 29, 2019 at 09:23:53AM +1000, Paul Mackerras wrote:
> Paolo or Radim,
> 
> Please do a pull from my kvm-ppc-next-5.4-1 tag to get a PPC KVM
> update for 5.4.  There is not a lot this time, mostly minor fixes and
> some prep for future patch series, plus a series that fixes a race
> condition in the XIVE interrupt controller code where interrupts could
> arrive after free_irq() and cause hangs and crashes in the host.
> 
> The XIVE fix touches both PPC KVM and generic powerpc code, so Michael
> Ellerman put it in his topic/ppc-kvm branch and I have merged that
> branch into my kvm-ppc-next branch.

Ping?

> Thanks,
> Paul.
> 
> The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:
> 
>   Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.4-1
> 
> for you to fetch changes up to ff42df49e75f053a8a6b4c2533100cdcc23afe69:
> 
>   KVM: PPC: Book3S HV: Don't lose pending doorbell request on migration on P9 (2019-08-27 14:08:22 +1000)
> 
> ----------------------------------------------------------------
> PPC KVM update for 5.4
> 
> - Some prep for extending the uses of the rmap array
> - Various minor fixes
> - Commits from the powerpc topic/ppc-kvm branch, which fix a problem
>   with interrupts arriving after free_irq, causing host hangs and crashes.
> 
> ----------------------------------------------------------------
> Cédric Le Goater (1):
>       KVM: PPC: Book3S HV: XIVE: Free escalation interrupts before disabling the VP
> 
> Fabiano Rosas (1):
>       KVM: PPC: Remove leftover comment from emulate_loadstore.c
> 
> Mark Cave-Ayland (1):
>       KVM: PPC: Book3S PR: Fix software breakpoints
> 
> Paul Mackerras (7):
>       KVM: PPC: Book3S HV: Fix race in re-enabling XIVE escalation interrupts
>       KVM: PPC: Book3S HV: Don't push XIVE context when not using XIVE device
>       powerpc/xive: Implement get_irqchip_state method for XIVE to fix shutdown race
>       Merge remote-tracking branch 'remotes/powerpc/topic/ppc-kvm' into kvm-ppc-next
>       KVM: PPC: Book3S: Enable XIVE native capability only if OPAL has required functions
>       KVM: PPC: Book3S HV: Check for MMU ready on piggybacked virtual cores
>       KVM: PPC: Book3S HV: Don't lose pending doorbell request on migration on P9
> 
> Paul Menzel (1):
>       KVM: PPC: Book3S: Mark expected switch fall-through
> 
> Suraj Jitindar Singh (1):
>       KVM: PPC: Book3S HV: Define usage types for rmap array in guest memslot
> 
>  arch/powerpc/include/asm/kvm_host.h     | 22 +++++++--
>  arch/powerpc/include/asm/kvm_ppc.h      |  1 +
>  arch/powerpc/include/asm/xive.h         |  9 ++++
>  arch/powerpc/kvm/book3s.c               |  8 +--
>  arch/powerpc/kvm/book3s_32_mmu.c        |  1 +
>  arch/powerpc/kvm/book3s_hv.c            | 24 ++++++---
>  arch/powerpc/kvm/book3s_hv_rm_mmu.c     |  2 +-
>  arch/powerpc/kvm/book3s_hv_rmhandlers.S | 38 +++++++++-----
>  arch/powerpc/kvm/book3s_xive.c          | 60 +++++++++++++++++++----
>  arch/powerpc/kvm/book3s_xive.h          |  2 +
>  arch/powerpc/kvm/book3s_xive_native.c   | 23 +++++++--
>  arch/powerpc/kvm/emulate.c              |  1 +
>  arch/powerpc/kvm/emulate_loadstore.c    |  6 ---
>  arch/powerpc/kvm/powerpc.c              |  3 +-
>  arch/powerpc/sysdev/xive/common.c       | 87 ++++++++++++++++++++++++---------
>  arch/powerpc/sysdev/xive/native.c       |  7 +++
>  16 files changed, 223 insertions(+), 71 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, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-5.4-1 tag
Date: Fri, 6 Sep 2019 22:04:15 +1000	[thread overview]
Message-ID: <20190906120415.GA1625@blackberry> (raw)
In-Reply-To: <20190828232353.GA4485@blackberry>

On Thu, Aug 29, 2019 at 09:23:53AM +1000, Paul Mackerras wrote:
> Paolo or Radim,
> 
> Please do a pull from my kvm-ppc-next-5.4-1 tag to get a PPC KVM
> update for 5.4.  There is not a lot this time, mostly minor fixes and
> some prep for future patch series, plus a series that fixes a race
> condition in the XIVE interrupt controller code where interrupts could
> arrive after free_irq() and cause hangs and crashes in the host.
> 
> The XIVE fix touches both PPC KVM and generic powerpc code, so Michael
> Ellerman put it in his topic/ppc-kvm branch and I have merged that
> branch into my kvm-ppc-next branch.

Ping?

> Thanks,
> Paul.
> 
> The following changes since commit 609488bc979f99f805f34e9a32c1e3b71179d10b:
> 
>   Linux 5.3-rc2 (2019-07-28 12:47:02 -0700)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.4-1
> 
> for you to fetch changes up to ff42df49e75f053a8a6b4c2533100cdcc23afe69:
> 
>   KVM: PPC: Book3S HV: Don't lose pending doorbell request on migration on P9 (2019-08-27 14:08:22 +1000)
> 
> ----------------------------------------------------------------
> PPC KVM update for 5.4
> 
> - Some prep for extending the uses of the rmap array
> - Various minor fixes
> - Commits from the powerpc topic/ppc-kvm branch, which fix a problem
>   with interrupts arriving after free_irq, causing host hangs and crashes.
> 
> ----------------------------------------------------------------
> Cédric Le Goater (1):
>       KVM: PPC: Book3S HV: XIVE: Free escalation interrupts before disabling the VP
> 
> Fabiano Rosas (1):
>       KVM: PPC: Remove leftover comment from emulate_loadstore.c
> 
> Mark Cave-Ayland (1):
>       KVM: PPC: Book3S PR: Fix software breakpoints
> 
> Paul Mackerras (7):
>       KVM: PPC: Book3S HV: Fix race in re-enabling XIVE escalation interrupts
>       KVM: PPC: Book3S HV: Don't push XIVE context when not using XIVE device
>       powerpc/xive: Implement get_irqchip_state method for XIVE to fix shutdown race
>       Merge remote-tracking branch 'remotes/powerpc/topic/ppc-kvm' into kvm-ppc-next
>       KVM: PPC: Book3S: Enable XIVE native capability only if OPAL has required functions
>       KVM: PPC: Book3S HV: Check for MMU ready on piggybacked virtual cores
>       KVM: PPC: Book3S HV: Don't lose pending doorbell request on migration on P9
> 
> Paul Menzel (1):
>       KVM: PPC: Book3S: Mark expected switch fall-through
> 
> Suraj Jitindar Singh (1):
>       KVM: PPC: Book3S HV: Define usage types for rmap array in guest memslot
> 
>  arch/powerpc/include/asm/kvm_host.h     | 22 +++++++--
>  arch/powerpc/include/asm/kvm_ppc.h      |  1 +
>  arch/powerpc/include/asm/xive.h         |  9 ++++
>  arch/powerpc/kvm/book3s.c               |  8 +--
>  arch/powerpc/kvm/book3s_32_mmu.c        |  1 +
>  arch/powerpc/kvm/book3s_hv.c            | 24 ++++++---
>  arch/powerpc/kvm/book3s_hv_rm_mmu.c     |  2 +-
>  arch/powerpc/kvm/book3s_hv_rmhandlers.S | 38 +++++++++-----
>  arch/powerpc/kvm/book3s_xive.c          | 60 +++++++++++++++++++----
>  arch/powerpc/kvm/book3s_xive.h          |  2 +
>  arch/powerpc/kvm/book3s_xive_native.c   | 23 +++++++--
>  arch/powerpc/kvm/emulate.c              |  1 +
>  arch/powerpc/kvm/emulate_loadstore.c    |  6 ---
>  arch/powerpc/kvm/powerpc.c              |  3 +-
>  arch/powerpc/sysdev/xive/common.c       | 87 ++++++++++++++++++++++++---------
>  arch/powerpc/sysdev/xive/native.c       |  7 +++
>  16 files changed, 223 insertions(+), 71 deletions(-)

  reply	other threads:[~2019-09-06 12:04 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22  5:14 [GIT PULL] Please pull my kvm-ppc-next-5.1-1 tag Paul Mackerras
2019-02-22  5:23 ` Masahiro Yamada
2019-02-22  5:52 ` Paul Mackerras
2019-02-22  6:46 ` Masahiro Yamada
2019-02-22  9:46 ` Paul Mackerras
2019-02-22 16:43 ` Paolo Bonzini
2019-03-01  3:37 ` [GIT PULL] Please pull my kvm-ppc-next-5.1-2 tag Paul Mackerras
2019-03-01  5:21 ` [GIT PULL] Please pull my kvm-ppc-next-5.1-3 tag Paul Mackerras
2019-03-14  3:31 ` Paul Mackerras
2019-03-15 18:13 ` Paolo Bonzini
2019-05-02  4:06 ` [GIT PULL] Please pull my kvm-ppc-next-5.2-1 tag Paul Mackerras
2019-05-02  4:06   ` Paul Mackerras
2019-05-09 22:46   ` Paul Mackerras
2019-05-09 22:46     ` Paul Mackerras
2019-05-14 10:13 ` [GIT PULL] Please pull my kvm-ppc-next-5.2-2 tag Paul Mackerras
2019-05-14 10:13   ` Paul Mackerras
2019-05-15 21:40   ` Paolo Bonzini
2019-05-15 21:40     ` Paolo Bonzini
2019-08-28 23:23 ` [GIT PULL] Please pull my kvm-ppc-next-5.4-1 tag Paul Mackerras
2019-08-28 23:23   ` Paul Mackerras
2019-09-06 12:04   ` Paul Mackerras [this message]
2019-09-06 12:04     ` Paul Mackerras
2019-09-10 14:51     ` Paolo Bonzini
2019-09-10 14:51       ` Paolo Bonzini
2019-10-31 11:13 ` [GIT PULL] Please pull my kvm-ppc-next-5.5-1 tag Paul Mackerras
2019-10-31 11:13   ` Paul Mackerras
2019-10-31 23:36   ` Paolo Bonzini
2019-10-31 23:36     ` Paolo Bonzini
2019-11-25  0:58 ` [GIT PULL] Please pull my kvm-ppc-next-5.5-2 tag Paul Mackerras
2019-11-25  0:58   ` Paul Mackerras
2019-11-25 10:29   ` Paolo Bonzini
2019-11-25 10:29     ` Paolo Bonzini
2019-11-25 23:44     ` Paul Mackerras
2019-11-25 23:44       ` Paul Mackerras
2019-11-26  8:52       ` Paolo Bonzini
2019-11-26  8:52         ` Paolo Bonzini
2020-01-21  3:33 ` [GIT PULL] Please pull my kvm-ppc-next-5.6-1 tag Paul Mackerras
2020-01-21  3:33   ` Paul Mackerras
2020-01-21 16:15   ` Paolo Bonzini
2020-01-21 16:15     ` Paolo Bonzini
2020-01-30  0:54 ` [GIT PULL] Please pull my kvm-ppc-next-5.6-2 tag Paul Mackerras
2020-01-30  0:54   ` Paul Mackerras
2020-03-30 23:08 ` [GIT PULL] Please pull my kvm-ppc-next-5.7-1 tag Paul Mackerras
2020-03-30 23:08   ` Paul Mackerras
2020-03-31 14:47   ` Paolo Bonzini
2020-03-31 14:47     ` Paolo Bonzini
2020-06-01 23:53 ` [GIT PULL] Please pull my kvm-ppc-next-5.8-1 tag Paul Mackerras
2020-06-01 23:53   ` Paul Mackerras
2020-06-04 18:58   ` Paolo Bonzini
2020-06-04 18:58     ` Paolo Bonzini
2020-06-11  0:48     ` Paul Mackerras
2020-06-11  0:48       ` Paul Mackerras
2020-06-11  1:01       ` Paolo Bonzini
2020-06-11  1:01         ` Paolo Bonzini
2020-07-28  5:51 ` [GIT PULL] Please pull my kvm-ppc-next-5.9-1 tag Paul Mackerras
2020-07-28  5:51   ` Paul Mackerras
2020-08-05  0:02   ` Paul Mackerras
2020-08-05  0:02     ` Paul Mackerras
2020-08-07 12:23     ` Paolo Bonzini
2020-08-07 12:23       ` Paolo Bonzini
2020-09-22  4:19 ` [GIT PULL] Please pull my kvm-ppc-next-5.10-1 tag Paul Mackerras
2020-09-22  4:19   ` Paul Mackerras
2020-09-22 12:18   ` Paolo Bonzini
2020-09-22 12:18     ` Paolo Bonzini
2021-02-11  7:25 ` [GIT PULL] Please pull my kvm-ppc-next-5.12-1 tag Paul Mackerras
2021-02-11  7:25   ` Paul Mackerras
2021-02-11 13:00   ` Paolo Bonzini
2021-02-11 13:00     ` 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=20190906120415.GA1625@blackberry \
    --to=paulus@ozlabs.org \
    --cc=david@gibson.dropbear.id.au \
    --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: link
Be 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.