From: "Radim Krčmář" <rkrcmar@redhat.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [GIT PULL] Please pull my kvm-ppc-next-4.17-1 tag
Date: Thu, 29 Mar 2018 20:34:05 +0000 [thread overview]
Message-ID: <20180329203405.GA27079@flask> (raw)
In-Reply-To: <20180119044850.GA10633@fergus.ozlabs.ibm.com>
2018-03-29 16:38+1100, Paul Mackerras:
> Paolo or Radim,
>
> Please do a pull from my kvm-ppc-next-4.17-1 tag to get a PPC KVM
> update for the 4.17 merge window. What's in here is a series that
> improves the radix page fault handler for POWER9 systems and makes it
> use the generic __gfn_to_pfn_memslot() function. At this stage I am
> just using that function as-is without the changes we discussed some
> time ago; that can be optimized in future.
>
> There are two other series that affect PPC KVM and also other powerpc
> code. Michael Ellerman has put them in the topic/ppc-kvm branch in his
> powerpc tree and merged them into his next branch. I have not merged
> that topic branch into my kvm-ppc-next branch because there were no
> conflicts to resolve and so those changes might as well just go in
> through Michael's tree. There was a series that adds hypervisor
> assistance for transactional memory, allowing KVM guests to use TM on
> POWER9 systems, and a series that disables use of data watchpoints on
> POWER9 because of hardware bugs.
Pulled, thanks.
next prev parent reply other threads:[~2018-03-29 20:34 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ář [this message]
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 ` [GIT PULL] Please pull my kvm-ppc-next-4.21-2 tag Paul Mackerras
2018-12-21 10:48 ` 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=20180329203405.GA27079@flask \
--to=rkrcmar@redhat.com \
--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.