From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [KVM PATCH v3 0/2] irqfd Date: Tue, 28 Apr 2009 23:10:02 -0700 Message-ID: <20090428231002.919419dd.akpm@linux-foundation.org> References: <20090427182540.6646.96740.stgit@dev.haskins.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, avi@redhat.com, davidel@xmailserver.org To: Gregory Haskins Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:47638 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752055AbZD2GOT (ORCPT ); Wed, 29 Apr 2009 02:14:19 -0400 In-Reply-To: <20090427182540.6646.96740.stgit@dev.haskins.net> Sender: kvm-owner@vger.kernel.org List-ID: On Mon, 27 Apr 2009 14:33:24 -0400 Gregory Haskins wrote: > (Applies to kvm.git 41b76d8d0487c26d6d4d3fe53c1ff59b3236f096) > > This series implements a mechanism called "irqfd". It lets you create > an eventfd based file-desriptor to inject interrupts to a kvm guest. We > associate one gsi per fd for fine-grained routing. It'd be nice if the KVM weenies amongst us were to be told why one would want to inject interrupts into a KVM guest. Monosyllabic words would be preferred ;) > We do not have a user of this interface in this series, though note > future version of virtual-bus (v4 and above) will be based on this. So I assume that this patchset will be merged if/when a user of it is merged? > The first patch will require mainline buy-in, particularly from Davide > (cc'd). The last patch is kvm specific. Three EXPORT_SYMBOL_GPL()s. Once the shouting has subsided I'd suggest that this be merged via the KVM tree.