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, Greg Kurz <groug@kaod.org>
Subject: [GIT PULL] Please pull my kvm-ppc-next-5.5-2 tag
Date: Mon, 25 Nov 2019 11:58:26 +1100 [thread overview]
Message-ID: <20191125005826.GA25463@oak.ozlabs.ibm.com> (raw)
Paolo,
Please do a pull from my kvm-ppc-next-5.5-2 tag to get two more
commits which should go upstream for 5.5. Although they are in my
kvm-ppc-next branch, they are actually bug fixes, fixing host memory
leaks in the XIVE interrupt controller code, so they should be fine to
go into v5.5 even though the merge window is now open.
Thanks,
Paul.
The following changes since commit 55d7004299eb917767761f01a208d50afad4f535:
KVM: PPC: Book3S HV: Reject mflags=2 (LPCR[AIL]=2) ADDR_TRANS_MODE mode (2019-10-22 16:29:02 +1100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.5-2
for you to fetch changes up to 30486e72093ea2e594f44876b7a445c219449bce:
KVM: PPC: Book3S HV: XIVE: Fix potential page leak on error path (2019-11-21 16:24:41 +1100)
----------------------------------------------------------------
Second KVM PPC update for 5.5
- Two fixes from Greg Kurz to fix memory leak bugs in the XIVE code.
----------------------------------------------------------------
Greg Kurz (2):
KVM: PPC: Book3S HV: XIVE: Free previous EQ page when setting up a new one
KVM: PPC: Book3S HV: XIVE: Fix potential page leak on error path
arch/powerpc/kvm/book3s_xive_native.c | 44 +++++++++++++++++++++++------------
1 file changed, 29 insertions(+), 15 deletions(-)
next reply other threads:[~2019-11-25 0:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 0:58 Paul Mackerras [this message]
2019-11-25 10:29 ` [GIT PULL] Please pull my kvm-ppc-next-5.5-2 tag Paolo Bonzini
2019-11-25 23:44 ` Paul Mackerras
2019-11-26 8:52 ` 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=20191125005826.GA25463@oak.ozlabs.ibm.com \
--to=paulus@ozlabs.org \
--cc=groug@kaod.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox