From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCHv0 RFC] kvm: irqfd support for level interrupts Date: Wed, 19 Aug 2009 15:17:22 +0300 Message-ID: <4A8BED52.8080005@redhat.com> References: <20090726162225.GA21972@redhat.com> <20090727053312.GC20501@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , mtosatti@redhat.com, kvm@vger.kernel.org To: Gleb Natapov Return-path: Received: from mx2.redhat.com ([66.187.237.31]:54297 "EHLO mx2.redhat.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1750853AbZHSMRX (ORCPT ); Wed, 19 Aug 2009 08:17:23 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n7JCHPAQ032494 for ; Wed, 19 Aug 2009 08:17:25 -0400 In-Reply-To: <20090727053312.GC20501@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/27/2009 08:33 AM, Gleb Natapov wrote: > On Sun, Jul 26, 2009 at 07:22:25PM +0300, Michael S. Tsirkin wrote: > >> Here's an untested patch with partial support for level triggered >> interrupts in irqfd. What this patch has: support for clearing interrupt >> on ack. What this patch does not have: support signalling eventfd on ack >> so that userspace can take action and e.g. reenable interrupt. >> >> > Do we want level triggered irqfd to be used only for device assignment? > If it works, it should work everywhere. -- error compiling committee.c: too many arguments to function