public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: kvm@vger.kernel.org, viro@ZenIV.linux.org.uk,
	linux-kernel@vger.kernel.org, davidel@xmailserver.org
Subject: Re: [KVM PATCH v4 2/2] kvm: add support for irqfd via	eventfd-notification interface
Date: Tue, 05 May 2009 18:45:09 +0300	[thread overview]
Message-ID: <4A005F05.30409@redhat.com> (raw)
In-Reply-To: <20090504175750.26758.7023.stgit@dev.haskins.net>

Gregory Haskins wrote:
> KVM provides a complete virtual system environment for guests, including
> support for injecting interrupts modeled after the real exception/interrupt
> facilities present on the native platform (such as the IDT on x86).
> Virtual interrupts can come from a variety of sources (emulated devices,
> pass-through devices, etc) but all must be injected to the guest via
> the KVM infrastructure.  This patch adds a new mechanism to inject a specific
> interrupt to a guest using a decoupled eventfd mechnanism:  Any legal signal
> on the irqfd (using eventfd semantics from either userspace or kernel) will
> translate into an injected interrupt in the guest at the next available
> interrupt window.
>
>  
> +struct kvm_irqfd {
> +	__u32 gsi;
> +	__u32 flags;
> +};
> +
>   

Please add some reserved space here.

> +int
> +kvm_irqfd(struct kvm *kvm, int gsi, int flags)
> +{
> +	struct _irqfd *irqfd;
> +	struct file *file = NULL;
> +	int fd = -1;
> +	int ret;
> +
> +	irqfd = kzalloc(sizeof(*irqfd), GFP_KERNEL);
> +	if (!irqfd)
> +		return -ENOMEM;
> +
> +	irqfd->kvm = kvm;
>   

You need to increase the refcount on struct kvm here.  Otherwise evil 
userspace will create an irqfd, close the vm and vcpu fds, and inject an 
interrupt.

Otherwise, looks good.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-05-05 15:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 17:57 [KVM PATCH v4 0/2] irqfd Gregory Haskins
2009-05-04 17:57 ` [KVM PATCH v4 1/2] eventfd: export eventfd interfaces for module use Gregory Haskins
2009-05-04 22:24   ` Al Viro
2009-05-05  2:17     ` Gregory Haskins
2009-05-04 17:57 ` [KVM PATCH v4 2/2] kvm: add support for irqfd via eventfd-notification interface Gregory Haskins
2009-05-05 15:45   ` Avi Kivity [this message]
2009-05-05 17:34     ` Gregory Haskins
2009-05-05 17:43       ` Avi Kivity
2009-05-05 17:56     ` Gregory Haskins
2009-05-05 18:10       ` Avi Kivity
2009-05-05 18:21         ` Gregory Haskins
2009-05-06 11:35   ` Gregory Haskins
2009-05-06 15:24     ` Davide Libenzi
2009-05-06 15:37       ` Gregory Haskins
2009-05-07  1:34         ` Davide Libenzi
2009-05-07  2:06           ` Gregory Haskins
2009-05-08 15:06             ` Davide Libenzi
2009-05-12  3:55               ` Gregory Haskins
2009-05-12  6:55                 ` Davide Libenzi
2009-05-07  9:48           ` Avi Kivity
2009-05-07 13:46             ` Marcelo Tosatti
2009-05-07 14:01               ` Gregory Haskins
2009-05-07 14:34                 ` Avi Kivity
2009-05-07 14:54                   ` Gregory Haskins
2009-05-07 15:26                     ` Avi Kivity
2009-05-07 14:46             ` Davide Libenzi
2009-05-07 15:47               ` Avi Kivity
2009-05-07 16:44                 ` Davide Libenzi
2009-05-07 18:12                   ` Avi Kivity
2009-05-08  3:13             ` Davide Libenzi
2009-05-08  8:19               ` Avi Kivity
2009-05-04 18:06 ` [KVM PATCH v4 0/2] irqfd Gregory Haskins
2009-05-04 18:52 ` Gregory Haskins
2009-05-05 14:16 ` Davide Libenzi
2009-05-05 14:27   ` Gregory Haskins

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=4A005F05.30409@redhat.com \
    --to=avi@redhat.com \
    --cc=davidel@xmailserver.org \
    --cc=ghaskins@novell.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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