From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Subject: Re: [PATCH resend] KVM: Document KVM_IRQFD Date: Mon, 29 Aug 2011 16:52:32 -0500 Message-ID: <4E5C0A20.4060408@freescale.com> References: <1314621244-4360-1-git-send-email-levinsasha928@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: , Avi Kivity , Marcelo Tosatti To: Sasha Levin Return-path: Received: from am1ehsobe005.messaging.microsoft.com ([213.199.154.208]:59614 "EHLO AM1EHSOBE005.bigfish.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753977Ab1H2Vwk (ORCPT ); Mon, 29 Aug 2011 17:52:40 -0400 In-Reply-To: <1314621244-4360-1-git-send-email-levinsasha928@gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08/29/2011 07:34 AM, Sasha Levin wrote: > Cc: Avi Kivity > Cc: Marcelo Tosatti > Signed-off-by: Sasha Levin > --- > 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