From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/2] eventfd: new EFD_STATE flag Date: Sun, 23 Aug 2009 16:01:29 +0300 Message-ID: <4A913DA9.1020403@redhat.com> References: <20090820155655.GA8764@redhat.com> <4A8D8A28.2050004@redhat.com> <20090820175540.GA9232@redhat.com> <4A8D90BB.2030506@redhat.com> <20090820182847.GB9282@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Davide Libenzi , gleb@redhat.com, kvm@vger.kernel.org, Linux Kernel Mailing List To: "Michael S. Tsirkin" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:16129 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933531AbZHWNBb (ORCPT ); Sun, 23 Aug 2009 09:01:31 -0400 In-Reply-To: <20090820182847.GB9282@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 08/20/2009 09:28 PM, Michael S. Tsirkin wrote: >>> I thought the point was to move assigned devices out of KVM? >>> >>> >> Grr. Forgot about that. >> >> That's much more important. >> > Looks like we'll have do with a separate char device or > something? > We can still tunnel it through userspace. Most assigned devices will have MSI. uio can signal the eventfd when the level changes, qemu can read the level and write it to kvm. -- error compiling committee.c: too many arguments to function