From: Paolo Bonzini <pbonzini@redhat.com>
To: "Christian Borntraeger" <borntraeger@de.ibm.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [GIT PULL 0/4] KVM: s390: Guarded storage fixup and keyless subset mode (kvm/next)
Date: Fri, 21 Apr 2017 12:28:35 +0200 [thread overview]
Message-ID: <a8a7b6d2-89f3-03e7-89c2-12e48694aeb4@redhat.com> (raw)
In-Reply-To: <1492769385-237420-1-git-send-email-borntraeger@de.ibm.com>
On 21/04/2017 12:09, Christian Borntraeger wrote:
> Paolo, Radim,
>
> here are 4 patches for s390 for 4.12 via kvm/next.
> 2 things
> - 2 fixups for guarded storage
> - detect and implement the keyless subset mode
> - there is one s390 sclp patch as a pre-req. It does not cause any
> conflict with todays linux-next and is acked by Martin
>
> please pull into kvm/next
>
> The following changes since commit f7b1a77d3bfbdc7e91a1e48e0a3dc10e7d890e04:
>
> Merge tag 'kvm-s390-next-4.12-1' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux (2017-04-11 20:54:40 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-4.12-2
>
> for you to fetch changes up to 730cd632c4e485b90f97fe998e300045da094938:
>
> KVM: s390: Support keyless subset guest mode (2017-04-21 11:08:11 +0200)
>
> ----------------------------------------------------------------
> KVM: s390: Guarded storage fixup and keyless subset mode
>
> - detect and use the keyless subset mode (guests without
> storage keys)
> - fix vSIE support for sdnxc
> - fix machine check data for guarded storage
>
> ----------------------------------------------------------------
> Christian Borntraeger (2):
> KVM: s390: Fix sdnxo setting for nested guests
> KVM: s390: fix stale machine check data for guarded storage
>
> Farhan Ali (2):
> s390/sclp: Detect KSS facility
> KVM: s390: Support keyless subset guest mode
>
> arch/s390/include/asm/kvm_host.h | 2 ++
> arch/s390/include/asm/sclp.h | 1 +
> arch/s390/include/uapi/asm/kvm.h | 1 +
> arch/s390/kvm/intercept.c | 3 +++
> arch/s390/kvm/interrupt.c | 2 ++
> arch/s390/kvm/kvm-s390.c | 8 +++++++-
> arch/s390/kvm/kvm-s390.h | 1 +
> arch/s390/kvm/priv.c | 19 +++++++++++++------
> arch/s390/kvm/vsie.c | 8 ++++++--
> drivers/s390/char/sclp_early.c | 4 +++-
> 10 files changed, 39 insertions(+), 10 deletions(-)
>
>
Pulled, thanks.
Paolo
prev parent reply other threads:[~2017-04-21 10:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:09 [GIT PULL 0/4] KVM: s390: Guarded storage fixup and keyless subset mode (kvm/next) Christian Borntraeger
2017-04-21 10:09 ` [GIT PULL 1/4] KVM: s390: Fix sdnxo setting for nested guests Christian Borntraeger
2017-04-21 10:09 ` [GIT PULL 2/4] KVM: s390: fix stale machine check data for guarded storage Christian Borntraeger
2017-04-21 10:09 ` [GIT PULL 3/4] s390/sclp: Detect KSS facility Christian Borntraeger
2017-04-21 10:09 ` [GIT PULL 4/4] KVM: s390: Support keyless subset guest mode Christian Borntraeger
2017-04-21 12:15 ` David Hildenbrand
2017-04-21 12:23 ` Christian Borntraeger
2017-04-21 12:29 ` David Hildenbrand
2017-04-21 10:28 ` 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=a8a7b6d2-89f3-03e7-89c2-12e48694aeb4@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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