* [PATCH-RFC 0/2] eventfd: new EFD_STATE flag
@ 2009-07-28 17:54 Michael S. Tsirkin
0 siblings, 0 replies; only message in thread
From: Michael S. Tsirkin @ 2009-07-28 17:54 UTC (permalink / raw)
To: davidel, avi, gleb, kvm, linux-kernel
Davide, all,
This RFC series implements a new EFD_STATE flag for eventfd.
When set, this changes eventfd behaviour in the following way:
- write simply stores the value written, and is always non-blocking
- read unblocks when the value written changes, and
returns the value written
Motivation: we'd like to use eventfd in qemu to pass interrupts from
(emulated or assigned) devices to guest. For level interrupts, the
counter supported currently by eventfd is not a good match: we really
need to set interrupt to a level, typically 0 or 1, wake the guest if
there was a change and and give the guest ability to see the last value
written.
Does extending eventfd in this way make sense? Please comment.
Michael S. Tsirkin (2):
eventfd: reorganize the code to simplify new flags
eventfd: EFD_STATE flag
fs/eventfd.c | 83 +++++++++++++++++++++++++++++++++++++++--------
include/linux/eventfd.h | 3 +-
2 files changed, 71 insertions(+), 15 deletions(-)
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2009-07-28 17:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-28 17:54 [PATCH-RFC 0/2] eventfd: new EFD_STATE flag Michael S. Tsirkin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).