From: Scott Wood <scottwood@freescale.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH resend] KVM: Document KVM_IRQFD
Date: Mon, 29 Aug 2011 16:52:32 -0500 [thread overview]
Message-ID: <4E5C0A20.4060408@freescale.com> (raw)
In-Reply-To: <1314621244-4360-1-git-send-email-levinsasha928@gmail.com>
On 08/29/2011 07:34 AM, Sasha Levin wrote:
> Cc: Avi Kivity <avi@redhat.com>
> Cc: Marcelo Tosatti <mtosatti@redhat.com>
> Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
> ---
> Documentation/virtual/kvm/api.txt | 27 +++++++++++++++++++++++++++
> 1 files changed, 27 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
> index 2d510b6..d1150b6 100644
> --- a/Documentation/virtual/kvm/api.txt
> +++ b/Documentation/virtual/kvm/api.txt
> @@ -1450,6 +1450,33 @@ is supported; 2 if the processor requires all virtual machines to have
> an RMA, or 1 if the processor can use an RMA but doesn't require it,
> because it supports the Virtual RMA (VRMA) facility.
>
> +4.64 KVM_IRQFD
> +
> +Capability: KVM_CAP_IRQFD
> +Architectures: all
> +Type: vm ioctl
> +Parameters: struct kvm_irqfd (in)
> +Returns: 0 on success, !0 on error
> +
> +This ioctl attaches or detaches an eventfd to a GSI within the guest.
> +While the eventfd is assigned to the guest, any write to the eventfd
> +would trigger the GSI within the guest.
> +
> +struct kvm_irqfd {
> + __u32 fd;
> + __u32 gsi;
> + __u32 flags;
> + __u8 pad[20];
> +};
Should define "gsi" (and how it's used by KVM) somewhere. AFAICT it's
an ACPI-ism.
-Scott
prev parent reply other threads:[~2011-08-29 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 12:34 [PATCH resend] KVM: Document KVM_IRQFD Sasha Levin
2011-08-29 12:37 ` Avi Kivity
2011-08-29 12:43 ` Sasha Levin
2011-08-29 12:50 ` Avi Kivity
2011-08-29 21:52 ` Scott Wood [this message]
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=4E5C0A20.4060408@freescale.com \
--to=scottwood@freescale.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mtosatti@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