From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Carsten Otte <cotte@de.ibm.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Sebastian Ott <sebott@linux.vnet.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Avi Kivity <avi@redhat.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: [Qemu-devel] [RFC PATCH v3 0/5] s390: Host support for channel I/O.
Date: Wed, 31 Oct 2012 17:24:33 +0100 [thread overview]
Message-ID: <1351700678-41969-1-git-send-email-cornelia.huck@de.ibm.com> (raw)
Hi,
here's the latest incarnation of my host patches to support channel
I/O on s390.
Most patches have only seen minor fixes, but patch 5 is completely
different since the kvm <-> user space interface has been reworked.
We now handle only interrupt-related operations in kvm. This
includes two channel I/O instructions that can dequeue pending I/O
interrupts: tpi and tsch (not the part actually interacting with
the subchannel). This makes the interface less complex (only one
new exit for tsch handling) and avoids duplicating code from qemu.
Cornelia Huck (5):
KVM: s390: Support for I/O interrupts.
KVM: s390: Add support for machine checks.
KVM: s390: In-kernel handling of I/O instructions.
KVM: s390: Base infrastructure for enabling capabilities.
KVM: s390: Add support for channel I/O instructions.
Documentation/virtual/kvm/api.txt | 40 +++++-
arch/s390/include/asm/kvm_host.h | 11 ++
arch/s390/kvm/intercept.c | 22 ++-
arch/s390/kvm/interrupt.c | 264 +++++++++++++++++++++++++++++++++++-
arch/s390/kvm/kvm-s390.c | 38 ++++++
arch/s390/kvm/kvm-s390.h | 6 +
arch/s390/kvm/priv.c | 275 +++++++++++++++++++++++++++++++++++---
arch/s390/kvm/trace-s390.h | 26 +++-
include/linux/kvm.h | 18 +++
include/trace/events/kvm.h | 2 +-
10 files changed, 673 insertions(+), 29 deletions(-)
--
1.7.12.4
next reply other threads:[~2012-10-31 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 16:24 Cornelia Huck [this message]
2012-10-31 16:24 ` [Qemu-devel] [PATCH 1/5] KVM: s390: Support for I/O interrupts Cornelia Huck
2012-10-31 16:24 ` [Qemu-devel] [PATCH 2/5] KVM: s390: Add support for machine checks Cornelia Huck
2012-10-31 16:24 ` [Qemu-devel] [PATCH 3/5] KVM: s390: In-kernel handling of I/O instructions Cornelia Huck
2012-10-31 16:24 ` [Qemu-devel] [PATCH 4/5] KVM: s390: Base infrastructure for enabling capabilities Cornelia Huck
2012-10-31 16:24 ` [Qemu-devel] [PATCH 5/5] KVM: s390: Add support for channel I/O instructions Cornelia Huck
2012-11-13 22:25 ` [Qemu-devel] [RFC PATCH v3 0/5] s390: Host support for channel I/O Marcelo Tosatti
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=1351700678-41969-1-git-send-email-cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.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).