From: Christian Borntraeger <borntraeger@de.ibm.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: KVM <kvm@vger.kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>,
David Hildenbrand <david@redhat.com>
Subject: [PATCH/RFC 0/2] KVM: s390: enable kvm_vpcu_kick/wake_up
Date: Fri, 17 Feb 2017 14:10:05 +0100 [thread overview]
Message-ID: <1487337007-91063-1-git-send-email-borntraeger@de.ibm.com> (raw)
David, I have certainly forgotten something, but I think
this should be good enough for all non-special cases that require
specific CPUs outside of the guest context and only need to handle
a request fast.
Christian Borntraeger (2):
s390/smp: export smp_send_reschedule
KVM: enable kvm_vcpu_kick/wake_up for s390
arch/s390/kernel/smp.c | 1 +
arch/s390/kvm/kvm-s390.c | 12 ++++++++++--
virt/kvm/kvm_main.c | 2 --
3 files changed, 11 insertions(+), 4 deletions(-)
--
2.7.4
next reply other threads:[~2017-02-17 13:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 13:10 Christian Borntraeger [this message]
2017-02-17 13:10 ` [PATCH/RFC 1/2] s390/smp: export smp_send_reschedule Christian Borntraeger
2017-02-17 15:12 ` [PATCH] KVM: add kvm_arch_cpu_kick Radim Krčmář
2017-02-17 15:46 ` Christian Borntraeger
2017-02-17 16:23 ` Paolo Bonzini
2017-02-17 16:42 ` Christian Borntraeger
2017-02-17 17:10 ` David Hildenbrand
2017-02-20 11:12 ` Christian Borntraeger
2017-02-20 11:35 ` David Hildenbrand
2017-02-20 21:45 ` Radim Krčmář
2017-02-21 8:59 ` Christian Borntraeger
2017-02-21 17:15 ` Radim Krčmář
2017-02-21 19:08 ` Christian Borntraeger
2017-02-22 15:29 ` Radim Krčmář
2017-02-20 20:59 ` Radim Krčmář
2017-02-17 17:07 ` David Hildenbrand
2017-02-17 13:10 ` [PATCH/RFC 2/2] KVM: enable kvm_vcpu_kick/wake_up for s390 Christian Borntraeger
2017-02-17 15:23 ` Radim Krčmář
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=1487337007-91063-1-git-send-email-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--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