From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56703) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WS2JA-0004Xk-V5 for qemu-devel@nongnu.org; Mon, 24 Mar 2014 06:40:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WS2J4-000319-BC for qemu-devel@nongnu.org; Mon, 24 Mar 2014 06:40:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:13634) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WS2J3-00030U-Lb for qemu-devel@nongnu.org; Mon, 24 Mar 2014 06:40:38 -0400 Message-ID: <53300B90.7090301@redhat.com> Date: Mon, 24 Mar 2014 11:40:16 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1395406341-14698-1-git-send-email-cornelia.huck@de.ibm.com> <532FF0E1.5000502@de.ibm.com> In-Reply-To: <532FF0E1.5000502@de.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 0/4] KVM: irqfds for s390 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christian Borntraeger , Cornelia Huck , kvm@vger.kernel.org, linux-s390@vger.kernel.org, qemu-devel@nongnu.org Cc: gleb@kernel.org, agraf@suse.de Il 24/03/2014 09:46, Christian Borntraeger ha scritto: >> > here's the next iteration of my patchset introducing irqfds for s390. >> > >> > Changes from v2: >> > - rebased against current kvm/queue >> > - kvm common code lock fix is already in queue >> > - move some changes that belonged in patch 2 from patch 3 >> > - add a limit for mapped pages to patch 2 >> > - collected some acks >> > >> > Changes from v1: >> > - rebased against current kvm/queue, bumping capability numbers >> > - guest adapter interrupt support is already in the kvm tree >> > >> > Again, find it on >> > >> > git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git kvms390-irqfd > Looks all good. > > Paolo, > > I guess this will miss the next merge window, but can you pull for kvm/queue > if you have no further comments? I think this can get into the next merge window, no problem. I plan to move kvm/queue -> kvm/next tomorrow or wednesday, and include this series. Paolo