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>,
virtualization@lists.linux-foundation.org
Subject: [Qemu-devel] [RFC PATCH v2] Adapter interrupts for virtio-ccw.
Date: Tue, 9 Jul 2013 13:33:50 +0200 [thread overview]
Message-ID: <1373369631-3148-1-git-send-email-cornelia.huck@de.ibm.com> (raw)
Hi,
here's again my proposal for adapter (thin) interrupt support for virtio-ccw
devices, originally posted at
http://marc.info/?l=linux-virtualization&m=137060143904927&w=2
The document is unchanged, only rebased against current master.
Cornelia Huck (1):
virtio-ccw: Document adapter interrupts.
virtio-spec.lyx | 147 +++++++++++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 144 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-07-09 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 11:33 Cornelia Huck [this message]
2013-07-09 11:33 ` [Qemu-devel] [RFC PATCH v2] virtio-ccw: Document adapter interrupts 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=1373369631-3148-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 \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).