From: Alex Williamson <alex.williamson@redhat.com>
To: avi@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
jan.kiszka@siemens.com, mst@redhat.com
Subject: [PATCH 2/4] kvm: Add missing KVM_IRQFD API documentation
Date: Fri, 22 Jun 2012 16:15:50 -0600 [thread overview]
Message-ID: <20120622221541.9858.37619.stgit@bling.home> (raw)
In-Reply-To: <20120622220040.9858.43665.stgit@bling.home>
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
Documentation/virtual/kvm/api.txt | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
index 310fe50..9b4cb2b 100644
--- a/Documentation/virtual/kvm/api.txt
+++ b/Documentation/virtual/kvm/api.txt
@@ -1965,6 +1965,23 @@ return the hash table order in the parameter. (If the guest is using
the virtualized real-mode area (VRMA) facility, the kernel will
re-create the VMRA HPTEs on the next KVM_RUN of any vcpu.)
+4.76 KVM_IRQFD
+
+Capability: KVM_CAP_IRQFD
+Architectures: x86
+Type: vm ioctl
+Parameters: struct kvm_irqfd (in)
+Returns: 0 on success, -1 on error
+
+Allows setting an eventfd to directly trigger a guest interrupt
+kvm_irqfd.fd specifies the file descriptor to use as the eventfd and
+kvm_irqfd.gsi specifies the irqchip pin toggled by this event. By
+default this interface only supports edge triggered interrupts,
+meaning the specified gsi is asserted and immediately de-asserted
+when the eventfd is triggered. Specifying KVM_IRQFD_FLAG_DEASSIGN
+removes the previously set irqfd matching both kvm_irqfd.fd and
+kvm_irqfd.gsi.
+
5. The kvm_run structure
------------------------
next prev parent reply other threads:[~2012-06-22 22:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 22:15 [PATCH 0/4] kvm: level triggered irqfd support Alex Williamson
2012-06-22 22:15 ` [PATCH 1/4] kvm: Pass kvm_irqfd to functions Alex Williamson
2012-06-22 22:15 ` Alex Williamson [this message]
2012-06-24 8:34 ` [PATCH 2/4] kvm: Add missing KVM_IRQFD API documentation Michael S. Tsirkin
2012-06-24 14:56 ` Alex Williamson
2012-06-24 15:46 ` Michael S. Tsirkin
2012-06-22 22:16 ` [PATCH 3/4] kvm: Extend irqfd to support level interrupts Alex Williamson
2012-06-24 8:28 ` Michael S. Tsirkin
2012-06-24 14:50 ` Alex Williamson
2012-06-24 15:45 ` Michael S. Tsirkin
2012-06-24 21:52 ` Alex Williamson
2012-06-24 10:29 ` Avi Kivity
2012-06-24 15:18 ` Alex Williamson
2012-06-24 15:49 ` Michael S. Tsirkin
2012-06-24 21:59 ` Alex Williamson
2012-06-24 23:02 ` Michael S. Tsirkin
2012-06-25 16:17 ` Alex Williamson
2012-06-25 20:13 ` Michael S. Tsirkin
2012-06-25 19:29 ` Alex Williamson
2012-06-22 22:16 ` [PATCH 4/4][RFC] kvm: eoi_eventfd Alex Williamson
2012-06-24 8:24 ` Michael S. Tsirkin
2012-06-24 14:47 ` Alex Williamson
2012-06-24 15:40 ` Michael S. Tsirkin
2012-06-24 21:50 ` Alex Williamson
2012-06-24 22:35 ` Michael S. Tsirkin
2012-06-25 16:09 ` Alex Williamson
2012-06-25 20:12 ` Michael S. Tsirkin
2012-06-24 12:56 ` Avi Kivity
2012-06-24 15:02 ` Alex Williamson
2012-06-28 16:27 ` Avi Kivity
2012-06-28 17:21 ` Alex Williamson
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=20120622221541.9858.37619.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@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