From: Paolo Bonzini <pbonzini@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Gleb Natapov <gleb@redhat.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [PATCH 0/8] KVM: s390: fixes and cleanup
Date: Thu, 12 Sep 2013 18:34:45 +0200 [thread overview]
Message-ID: <5231ED25.8050003@redhat.com> (raw)
In-Reply-To: <1378974829-46578-1-git-send-email-borntraeger@de.ibm.com>
Il 12/09/2013 10:33, Christian Borntraeger ha scritto:
> Paolo, Gleb,
>
> here is a bunch of patch for kvm on s390.
> The first 4 patches restructure the code to protect most of
> vcpu_run with the kvm->srcu lock. The old code was structured
> in way that adding the lock was more complicated than necessary,
> therefore, the rework.
>
> The last 4 patches deal with instruction intercept handling.
>
> Patches are against kvm.git queue. Please apply.
>
>
> Thomas Huth (8):
> KVM: s390: Remove dead "rerun vcpu" code
> KVM: s390: Split up __vcpu_run into three parts
> KVM: s390: Push run loop into __vcpu_run
> KVM: s390: Lock kvm->srcu at the appropriate places
> KVM: s390: Allow NULL parameter for kvm_s390_get_regs_rre
> KVM: s390: Helper for converting real addresses to absolute
> KVM: s390: Implement TEST BLOCK
> KVM: s390: Intercept SCK instruction
>
> arch/s390/include/asm/kvm_host.h | 1 -
> arch/s390/kvm/diag.c | 4 +-
> arch/s390/kvm/gaccess.h | 21 ++++++----
> arch/s390/kvm/intercept.c | 6 ---
> arch/s390/kvm/interrupt.c | 3 ++
> arch/s390/kvm/kvm-s390.c | 91 ++++++++++++++++++++++++++--------------
> arch/s390/kvm/kvm-s390.h | 9 ++--
> arch/s390/kvm/priv.c | 61 +++++++++++++++++++++++++++
> 8 files changed, 144 insertions(+), 52 deletions(-)
>
Applied to kvm/queue for 3.13, thanks.
Paolo
next prev parent reply other threads:[~2013-09-12 16:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 8:33 [PATCH 0/8] KVM: s390: fixes and cleanup Christian Borntraeger
2013-09-12 8:33 ` [PATCH 1/8] KVM: s390: Remove dead "rerun vcpu" code Christian Borntraeger
2013-09-12 8:33 ` [PATCH 2/8] KVM: s390: Split up __vcpu_run into three parts Christian Borntraeger
2013-09-12 8:59 ` Paolo Bonzini
2013-09-12 9:09 ` Christian Borntraeger
2013-09-12 9:13 ` Paolo Bonzini
2013-09-12 8:33 ` [PATCH 3/8] KVM: s390: Push run loop into __vcpu_run Christian Borntraeger
2013-09-12 8:33 ` [PATCH 4/8] KVM: s390: Lock kvm->srcu at the appropriate places Christian Borntraeger
2013-09-12 8:33 ` [PATCH 5/8] KVM: s390: Allow NULL parameter for kvm_s390_get_regs_rre Christian Borntraeger
2013-09-12 8:33 ` [PATCH 6/8] KVM: s390: Helper for converting real addresses to absolute Christian Borntraeger
2013-09-12 8:33 ` [PATCH 7/8] KVM: s390: Implement TEST BLOCK Christian Borntraeger
2013-09-12 8:33 ` [PATCH 8/8] KVM: s390: Intercept SCK instruction Christian Borntraeger
2013-09-12 16:34 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-26 13:03 [PATCH 0/8] KVM: s390: fixes and cleanup Christian Borntraeger
2013-07-29 7:05 ` 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=5231ED25.8050003@redhat.com \
--to=pbonzini@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=gleb@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.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).