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 <cohuck@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: [GIT PULL 0/6] KVM: s390: Fixes and improvements for 4.16
Date: Wed, 14 Feb 2018 17:19:12 +0100 [thread overview]
Message-ID: <b23c7ff2-0458-2505-1076-a37580527f19@redhat.com> (raw)
In-Reply-To: <20180214155636.60405-1-borntraeger@de.ibm.com>
On 14/02/2018 16:56, Christian Borntraeger wrote:
> Paolo, Radim,
>
> some fixes and improvements for 4.16. (via kvm/master).
> Either for features new in 4.16 or to improve the speculative
> execution handling.
Pulled, thanks. Should make it into rc2.
Paolo
> The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
>
> Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git tags/kvm-s390-master-4.16-1
>
> for you to fetch changes up to baabee67f4135e3de87bc874929ac50637aacb0d:
>
> KVM: s390: use switch vs jump table in interrupt.c (2018-02-14 13:53:43 +0000)
>
> ----------------------------------------------------------------
> KVM: s390: Fixes and improvements for 4.16
>
> - optimization for the exitless interrupt support that was merged
> in 4.16-rc1
> - improve the branch prediction blocking for nested KVM
> - replace some jump tables with switch statements to improve
> expoline performance
>
> ----------------------------------------------------------------
> Christian Borntraeger (5):
> KVM: s390: optimize wakeup for exitless interrupts
> KVM: s390: do not set intervention requests for GISA interrupts
> KVM: s390: force bp isolation for VSIE
> KVM: s390: use switch vs jump table in priv.c
> KVM: s390: use switch vs jump table in intercept.c
>
> David Hildenbrand (1):
> KVM: s390: use switch vs jump table in interrupt.c
>
> arch/s390/kvm/intercept.c | 51 +++++++------
> arch/s390/kvm/interrupt.c | 98 +++++++++++++++----------
> arch/s390/kvm/kvm-s390.h | 2 -
> arch/s390/kvm/priv.c | 183 +++++++++++++++++++++++-----------------------
> arch/s390/kvm/vsie.c | 20 +++++
> 5 files changed, 200 insertions(+), 154 deletions(-)
>
prev parent reply other threads:[~2018-02-14 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 15:56 [GIT PULL 0/6] KVM: s390: Fixes and improvements for 4.16 Christian Borntraeger
2018-02-14 15:56 ` [GIT PULL 1/6] KVM: s390: optimize wakeup for exitless interrupts Christian Borntraeger
2018-02-14 15:56 ` [GIT PULL 2/6] KVM: s390: do not set intervention requests for GISA interrupts Christian Borntraeger
2018-02-14 15:56 ` [GIT PULL 3/6] KVM: s390: force bp isolation for VSIE Christian Borntraeger
2018-02-14 15:56 ` [GIT PULL 4/6] KVM: s390: use switch vs jump table in priv.c Christian Borntraeger
2018-02-14 15:56 ` [GIT PULL 5/6] KVM: s390: use switch vs jump table in intercept.c Christian Borntraeger
2018-02-14 15:56 ` [GIT PULL 6/6] KVM: s390: use switch vs jump table in interrupt.c Christian Borntraeger
2018-02-14 16:19 ` 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=b23c7ff2-0458-2505-1076-a37580527f19@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).