From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: KVM <kvm@vger.kernel.org>, linux-s390 <linux-s390@vger.kernel.org>
Subject: [RFC PATCH v2 0/2] qemu: ioeventfd for virtio-ccw.
Date: Fri, 22 Feb 2013 13:09:58 +0100 [thread overview]
Message-ID: <1361535000-39210-1-git-send-email-cornelia.huck@de.ibm.com> (raw)
Here's the next version of ioeventfd support for virtio-ccw, again
against master.
v1 -> v2:
- Adapt to changed ioeventfd interface.
Cornelia Huck (2):
linux-headers: Update with ioeventfd changes.
virtio-ccw: Wire up ioeventfd.
hw/s390x/css.c | 2 +-
hw/s390x/css.h | 1 +
hw/s390x/virtio-ccw.c | 114 ++++++++++++++++++++++++++++++++++++++++++++++
hw/s390x/virtio-ccw.h | 7 +++
linux-headers/linux/kvm.h | 2 +
target-s390x/cpu.h | 16 +++++++
target-s390x/kvm.c | 18 ++++++++
7 files changed, 159 insertions(+), 1 deletion(-)
--
1.7.12.4
next reply other threads:[~2013-02-22 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 12:09 Cornelia Huck [this message]
2013-02-22 12:09 ` [RFC PATCH v2 1/2] linux-headers: Update with ioeventfd changes Cornelia Huck
2013-02-22 12:10 ` [RFC PATCH v2 2/2] virtio-ccw: Wire up ioeventfd Cornelia Huck
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=1361535000-39210-1-git-send-email-cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=qemu-devel@nongnu.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