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-fixes-4.16-1 tag
Date: Sat, 03 Mar 2018 09:17:17 +0000	[thread overview]
Message-ID: <20180303091717.GA14569@fergus.ozlabs.ibm.com> (raw)

Paolo or Radim,

Please do a pull from my kvm-ppc-fixes-4.16-1 tag to get some fixes
for PPC KVM which should go into 4.16.

Thanks,
Paul.

The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:

  Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-fixes-4.16-1

for you to fetch changes up to 61bd0f66ff92d5ce765ff9850fd3cbfec773c560:

  KVM: PPC: Book3S HV: Fix guest time accounting with VIRT_CPU_ACCOUNTING_GEN (2018-03-03 19:28:34 +1100)

----------------------------------------------------------------
Fixes for PPC KVM:

- Fix guest time accounting in the host
- Fix large-page backing for radix guests on POWER9
- Fix HPT guests on POWER9 backed by 2M or 1G pages
- Compile fixes for some configs and gcc versions

----------------------------------------------------------------
Laurent Vivier (1):
      KVM: PPC: Book3S HV: Fix guest time accounting with VIRT_CPU_ACCOUNTING_GEN

Paul Mackerras (4):
      KVM: PPC: Fix compile error that occurs when CONFIG_ALTIVEC=n
      KVM: PPC: Book3S: Fix compile error that occurs with some gcc versions
      KVM: PPC: Book3S HV: Fix handling of large pages in radix page fault handler
      KVM: PPC: Book3S HV: Fix VRMA initialization with 2MB or 1GB memory backing

 arch/powerpc/kvm/book3s_64_mmu_radix.c | 69 +++++++++++++++++++++-------------
 arch/powerpc/kvm/book3s_hv.c           | 17 +++++----
 arch/powerpc/kvm/powerpc.c             |  4 +-
 3 files changed, 55 insertions(+), 35 deletions(-)

             reply	other threads:[~2018-03-03  9:17 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03  9:17 Paul Mackerras [this message]
2018-03-06 17:08 ` [GIT PULL] Please pull my kvm-ppc-fixes-4.16-1 tag 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
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
2019-05-30 11:59 [GIT PULL] Please pull my kvm-ppc-fixes-5.2-1 tag Paul Mackerras
2019-05-30 11:59 ` Paul Mackerras
2019-05-31 22:48 ` Paolo Bonzini
2019-05-31 22:48   ` 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-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-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
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

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=20180303091717.GA14569@fergus.ozlabs.ibm.com \
    --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.