linux-kernel - Re: [KVM PATCH v3 0/2] irqfd

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 28 Apr 2009 23:10:02 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Gregory Haskins <ghaskins@...ell.com>
Cc:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org, avi@...hat.com,
	davidel@...ilserver.org
Subject: Re: [KVM PATCH v3 0/2] irqfd

On Mon, 27 Apr 2009 14:33:24 -0400 Gregory Haskins <ghaskins@...ell.com> 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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/