All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: kvm-ppc@vger.kernel.org
Subject: [GIT PULL] Please pull my kvm-ppc-next-4.21-2 tag
Date: Fri, 21 Dec 2018 04:24:28 +0000	[thread overview]
Message-ID: <20181221042428.GA21596@blackberry> (raw)
In-Reply-To: <20180119044850.GA10633@fergus.ozlabs.ibm.com>

Paolo or Radim,

Thanks for pulling the previous set of commits for 4.21.  Suraj
Jitindar Singh has just fixed several bugs in the page dirty tracking
for nested guests, and it seems worth while to try to get his series
in for 4.21.  So please do a pull from my tree again to get this patch
series.

Thanks,
Paul.

The following changes since commit 95d386c2d2e7660a6447df1507a9845665dab7d8:

  KVM: PPC: Book3S HV: Allow passthrough of an emulated device to an L3 guest (2018-12-17 11:33:50 +1100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-4.21-2

for you to fetch changes up to ae59a7e1945bc2245bbb587071ca737e00daf443:

  KVM: PPC: Book3S HV: Keep rc bits in shadow pgtable in sync with host (2018-12-21 14:42:07 +1100)

----------------------------------------------------------------
Second PPC KVM update for 4.21

This has 5 commits that fix page dirty tracking when running nested
HV KVM guests, from Suraj Jitindar Singh.

----------------------------------------------------------------
Suraj Jitindar Singh (5):
      KVM: PPC: Book3S HV: Hold kvm->mmu_lock across updating nested pte rc bits
      KVM: PPC: Book3S HV: Align gfn to L1 page size when inserting nest-rmap entry
      KVM: PPC: Book3S HV: Apply combination of host and l1 pte rc for nested guest
      KVM: PPC: Book3S HV: Introduce kvmhv_update_nest_rmap_rc_list()
      KVM: PPC: Book3S HV: Keep rc bits in shadow pgtable in sync with host

 arch/powerpc/include/asm/kvm_book3s.h    |  2 +
 arch/powerpc/include/asm/kvm_book3s_64.h |  3 ++
 arch/powerpc/kvm/book3s_64_mmu_radix.c   | 26 ++++++++---
 arch/powerpc/kvm/book3s_hv_nested.c      | 74 +++++++++++++++++++++++++++++---
 4 files changed, 93 insertions(+), 12 deletions(-)

  parent reply	other threads:[~2018-12-21  4:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-19  4:48 [GIT PULL] Please pull my kvm-ppc-next-4.16-1 tag Paul Mackerras
2018-01-19  4:48 ` Paul Mackerras
2018-02-01 15:17 ` Radim Krčmář
2018-02-01 15:17   ` Radim Krčmář
2018-03-29  5:38 ` [GIT PULL] Please pull my kvm-ppc-next-4.17-1 tag Paul Mackerras
2018-03-29 20:34 ` Radim Krčmář
2018-06-04  1:27 ` [GIT PULL] Please pull my kvm-ppc-next-4.18-1 tag Paul Mackerras
2018-06-13  5:51 ` [GIT PULL] Please pull my kvm-ppc-next-4.18-2 tag Paul Mackerras
2018-06-13 16:22 ` [GIT PULL] Please pull my kvm-ppc-next-4.18-1 tag Paolo Bonzini
2018-06-13 21:52 ` Paul Mackerras
2018-07-31  5:56 ` [GIT PULL] Please pull my kvm-ppc-next-4.19-1 tag Paul Mackerras
2018-08-02 11:56 ` Paolo Bonzini
2018-10-10  5:55 ` [GIT PULL] Please pull my kvm-ppc-next-4.20-1 tag Paul Mackerras
2018-10-10 16:38 ` Paolo Bonzini
2018-10-20 10:53 ` [GIT PULL] Please pull my kvm-ppc-next-4.20-2 tag Paul Mackerras
2018-10-21  9:47 ` Paolo Bonzini
2018-12-18  3:05 ` [GIT PULL] Please pull my kvm-ppc-next-4.21-1 tag Paul Mackerras
2018-12-20 13:58 ` Radim Krčmář
2018-12-21  4:24 ` Paul Mackerras [this message]
2018-12-21 10:48 ` [GIT PULL] Please pull my kvm-ppc-next-4.21-2 tag Paolo Bonzini
2018-02-09  9:41 [GIT PULL] Please pull my kvm-ppc-next-4.16-2 tag Paul Mackerras
2018-02-09  9:41 ` Paul Mackerras
2018-02-10 14:52 ` Radim Krčmář
2018-02-10 14:52   ` Radim Krčmář

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=20181221042428.GA21596@blackberry \
    --to=paulus@ozlabs.org \
    --cc=kvm-ppc@vger.kernel.org \
    /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.