From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: KVM <kvm@vger.kernel.org>, Gleb Natapov <gleb@kernel.org>,
Alexander Graf <agraf@suse.de>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [GIT PULL 0/4] KVM: s390: Fixes for kvm/next (3.19) and stable
Date: Fri, 07 Nov 2014 13:07:28 +0100 [thread overview]
Message-ID: <545CB600.2050900@redhat.com> (raw)
In-Reply-To: <1415360716-9670-1-git-send-email-borntraeger@de.ibm.com>
On 07/11/2014 12:45, Christian Borntraeger wrote:
> Paolo,
>
> here are some fixes for KVM on s390 for kvm/next. The first two patches
> have a stable tag and could also go via kvm/master - if you like.
>
> The following changes since commit 0df1f2487d2f0d04703f142813d53615d62a1da4:
>
> Linux 3.18-rc3 (2014-11-02 15:01:51 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-next-20141107
>
> for you to fetch changes up to 365dc1633521a32d55d839f56b41bb9a531d957a:
>
> ----------------------------------------------------------------
> KVM: s390: Fixes for kvm/next (3.19) and stable
>
> 1. We should flush TLBs for load control instruction emulation (stable)
> 2. A workaround for a compiler bug that renders ACCESS_ONCE broken (stable)
> 3. Fix program check handling for load control
> 4. Documentation Fix
>
> ----------------------------------------------------------------
> Christian Borntraeger (2):
> KVM: s390: Fix ipte locking
> KVM: s390: flush CPU on load control
>
> Dominik Dingel (1):
> KVM: fix vm device attribute documentation
>
> Heiko Carstens (1):
> KVM: s390: fix handling of lctl[g]/stctl[g]
>
> Documentation/virtual/kvm/devices/vm.txt | 10 ++---
> arch/s390/kvm/gaccess.c | 20 ++++++---
> arch/s390/kvm/priv.c | 72 +++++++++++++++-----------------
> 3 files changed, 53 insertions(+), 49 deletions(-)
>
Pulled to kvm/next (at least locally, I have tests running and will push
to kernel.org next Monday).
Paolo
prev parent reply other threads:[~2014-11-07 12:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 11:45 [GIT PULL 0/4] KVM: s390: Fixes for kvm/next (3.19) and stable Christian Borntraeger
2014-11-07 11:45 ` [GIT PULL 1/4] KVM: s390: Fix ipte locking Christian Borntraeger
2014-11-10 20:18 ` compiler bug gcc4.6/4.7 with ACCESS_ONCE and workarounds Christian Borntraeger
2014-11-10 21:07 ` Linus Torvalds
2014-11-11 0:37 ` Paul E. McKenney
2014-11-11 21:16 ` Christian Borntraeger
2014-11-12 0:33 ` Linus Torvalds
2014-11-12 0:36 ` Linus Torvalds
2014-11-12 8:05 ` Christian Borntraeger
2014-11-12 9:28 ` Martin Schwidefsky
2014-11-20 11:39 ` Christian Borntraeger
2014-11-20 20:30 ` Linus Torvalds
2014-11-07 11:45 ` [GIT PULL 2/4] KVM: s390: flush CPU on load control Christian Borntraeger
2014-11-07 11:45 ` [GIT PULL 3/4] KVM: s390: fix handling of lctl[g]/stctl[g] Christian Borntraeger
2014-11-07 11:45 ` [GIT PULL 4/4] KVM: fix vm device attribute documentation Christian Borntraeger
2014-11-07 12:07 ` 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=545CB600.2050900@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=gleb@kernel.org \
--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