From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCHv3 0/4] kvm: locking and API rework for iosignalfd Date: Mon, 29 Jun 2009 16:04:26 +0300 Message-ID: <4A48BBDA.2050904@redhat.com> References: <20090629120846.GA21273@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Gregory Haskins , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, mtosatti@redhat.com, paulmck@linux.vnet.ibm.com, markmc@redhat.com To: "Michael S. Tsirkin" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:58893 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753170AbZF2NDF (ORCPT ); Mon, 29 Jun 2009 09:03:05 -0400 In-Reply-To: <20090629120846.GA21273@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/29/2009 03:08 PM, Michael S. Tsirkin wrote: > This series switches kvm_io_device to slots_lock from kvm->lock mutex, > and uses that to rework io bus API. This takes less locks on data path, > and uses less lines of code. These changes will also be useful to serve > as basis for Greg's iosignalfd work. > Looks good to me. Marcelo? -- error compiling committee.c: too many arguments to function