From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [KVM PATCH v5 0/2] iosignalfd Date: Thu, 04 Jun 2009 15:25:13 +0300 Message-ID: <4A27BD29.3070709@redhat.com> References: <20090603200835.8206.8039.stgit@dev.haskins.net> <4A26ED22.4060203@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: mtosatti@redhat.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, davidel@xmailserver.org, paulmck@linux.vnet.ibm.com, markmc@redhat.com To: Gregory Haskins Return-path: Received: from mx2.redhat.com ([66.187.237.31]:58329 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752422AbZFDMZP (ORCPT ); Thu, 4 Jun 2009 08:25:15 -0400 In-Reply-To: <4A26ED22.4060203@novell.com> Sender: kvm-owner@vger.kernel.org List-ID: Gregory Haskins wrote: > Marcello, Avi, and myself have previously agreed that Marcello's > mmio-locking cleanup should go in first. When that happens, I will > need to rebase this series because it changes how you interface to the > io_bus code. I should have mentioned that here, but forgot. (Speaking > of, is there an ETA when that code will be merged Avi?) > I had issues with the unbalanced locking the patchset introduced in coalesced_mmio, once these are resolved the patchset will be merged. -- error compiling committee.c: too many arguments to function