From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [GIT PULL 0/4] KVM: s390 features and fixes for 4.5 (kvm/next)
Date: Wed, 16 Dec 2015 18:49:35 +0100 [thread overview]
Message-ID: <5671A42F.4070408@redhat.com> (raw)
In-Reply-To: <1450207426-17222-1-git-send-email-borntraeger@de.ibm.com>
On 15/12/2015 20:23, Christian Borntraeger wrote:
> Paolo,
>
> here is the 2nd part of the s390 queue for 4.5
>
> The following changes since commit 460146348518a1c4e810d01baf81847f8c6a1c73:
>
> Merge tag 'kvm-s390-next-4.5-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD (2015-12-02 13:50:04 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-4.5-2
>
> for you to fetch changes up to 32e6b236d26946eb076d1450bfb8f9978f15d6b9:
>
> KVM: s390: consider system MHA for guest storage (2015-12-15 17:08:22 +0100)
>
> ----------------------------------------------------------------
> KVM: s390 features and fixes for 4.5 (kvm/next)
>
> Some small cleanups
> - use assignment instead of memcpy
> - use %pK for kernel pointers
>
> Changes regarding guest memory size
> - Fix an off-by-one error in our guest memory interface (we might
> use unnecessarily big page tables, e.g. 3 levels for a 2GB guest
> instead of 2 levels)
> - We now ask the machine about the max. supported guest address
> and limit accordingly.
>
> ----------------------------------------------------------------
> Christian Borntraeger (2):
> KVM: s390: use assignment instead of memcpy
> KVM: s390: obey kptr_restrict in traces
>
> Dominik Dingel (1):
> KVM: s390: fix mismatch between user and in-kernel guest limit
>
> Guenther Hutzl (1):
> KVM: s390: consider system MHA for guest storage
>
> Documentation/virtual/kvm/devices/vm.txt | 3 ++-
> arch/s390/include/asm/kvm_host.h | 1 +
> arch/s390/include/uapi/asm/kvm.h | 2 ++
> arch/s390/kvm/kvm-s390.c | 44 ++++++++++++++++++++++++--------
> arch/s390/kvm/trace-s390.h | 6 ++---
> arch/s390/mm/pgtable.c | 4 +--
> drivers/s390/char/sclp_early.c | 8 +++++-
> 7 files changed, 50 insertions(+), 18 deletions(-)
>
Pulled (but not pushed yet), thanks.
Paolo
prev parent reply other threads:[~2015-12-16 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 19:23 [GIT PULL 0/4] KVM: s390 features and fixes for 4.5 (kvm/next) Christian Borntraeger
2015-12-15 19:23 ` [GIT PULL 1/4] KVM: s390: use assignment instead of memcpy Christian Borntraeger
2015-12-15 19:23 ` [GIT PULL 2/4] KVM: s390: obey kptr_restrict in traces Christian Borntraeger
2015-12-15 19:33 ` Kees Cook
2015-12-15 19:23 ` [GIT PULL 3/4] KVM: s390: fix mismatch between user and in-kernel guest limit Christian Borntraeger
2015-12-15 19:23 ` [GIT PULL 4/4] KVM: s390: consider system MHA for guest storage Christian Borntraeger
2015-12-16 17:49 ` Paolo Bonzini [this message]
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=5671A42F.4070408@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).