From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 5/5] ioeventfd: Introduce KVM_IOEVENTFD_FLAG_SOCKET Date: Tue, 12 Jul 2011 14:26:17 +0300 Message-ID: <4E1C2F59.90600@redhat.com> References: <1309927078-5983-1-git-send-email-levinsasha928@gmail.com> <1309927078-5983-5-git-send-email-levinsasha928@gmail.com> <20110706114203.GA18368@redhat.com> <1309964506.15123.13.camel@sasha> <20110706155135.GA21638@redhat.com> <1310276083.2393.6.camel@sasha> <20110710080559.GC1630@redhat.com> <1310469824.2393.22.camel@sasha> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , kvm@vger.kernel.org, Ingo Molnar , Marcelo Tosatti , Pekka Enberg To: Sasha Levin Return-path: Received: from mx1.redhat.com ([209.132.183.28]:23045 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752348Ab1GLL0j (ORCPT ); Tue, 12 Jul 2011 07:26:39 -0400 In-Reply-To: <1310469824.2393.22.camel@sasha> Sender: kvm-owner@vger.kernel.org List-ID: On 07/12/2011 02:23 PM, Sasha Levin wrote: > > > > I don't insist on a new type of exit, just pointing out the problem. > > I agree with you, I don't have a better solution either. > > I don't feel it's worth it adding so much code for read support to > properly work. Can we do this patch series without socket read support > at the moment? No. As I said before, I don't want a fragmented ABI. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.