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] [day] [month] [year] [list]
Date:	Tue, 12 May 2009 14:55:52 -0400
From:	Gregory Haskins <ghaskins@...ell.com>
To:	Avi Kivity <avi@...hat.com>
CC:	kvm@...r.kernel.org, viro@...IV.linux.org.uk,
	linux-kernel@...r.kernel.org, davidel@...ilserver.org
Subject: Re: [KVM PATCH v6] kvm: add support for irqfd

Avi Kivity wrote:
> Gregory Haskins wrote:
>> (Applies to kvm.git:833367b57)
>>
>> 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.
>>
>> I am reasonably satisfied with this series, so Avi please consider for
>> inclusion.
>>   
>
> Looks good.  Please add a way to disassociate an irqfd (for hotunplug)
> and I'll merge.
>
Done, and v7 sent out.  Since I completed the testing on the
"hypercall-fd" (I call them "iofd" for reasons described in the patch
headers) I included those as well for review.  Since the irqfd stuff is
heavily reviewed and the iofd patches haven't seen the light of day
until today, feel free to merge them independently.  I included them
together because I wanted to avoid forking the CAP bits, etc, for two
closely related subsystems.  But they technically don't need to go in
together if you prefer.

Thanks Avi,
-Greg


Download attachment "signature.asc" of type "application/pgp-signature" (267 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ