From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=58488 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PTH4s-0007BC-2R for qemu-devel@nongnu.org; Thu, 16 Dec 2010 11:53:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PTH4r-0007kR-2p for qemu-devel@nongnu.org; Thu, 16 Dec 2010 11:53:13 -0500 Received: from mx1.redhat.com ([209.132.183.28]:28405) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PTH4q-0007kL-R4 for qemu-devel@nongnu.org; Thu, 16 Dec 2010 11:53:13 -0500 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id oBGGrB3q014123 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 16 Dec 2010 11:53:12 -0500 Received: from rincewind.home.kraxel.org (vpn1-5-86.ams2.redhat.com [10.36.5.86]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id oBGGrApx017580 for ; Thu, 16 Dec 2010 11:53:11 -0500 Message-ID: <4D0A43F6.2020003@redhat.com> Date: Thu, 16 Dec 2010 17:53:10 +0100 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 1/1] spice: add chardev References: <1292498949-16933-1-git-send-email-alevy@redhat.com> <4D0A124C.6080108@redhat.com> <20101216164859.GA27251@playa.tlv.redhat.com> In-Reply-To: <20101216164859.GA27251@playa.tlv.redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, >>> +//#define SPICE_QEMU_CHAR_USE_IOCTL >> >> Why is this disabled? >> Does it depend on the chardev patches from Amit? >> > > There was a long discussion that concluded we don't want IOCTL's at all, > and that there should be some other mechanism for connection state > communication between the two sides. Meanwhile I found out I don't need > these (I don't remember exactly what I used instead, but basically just > the regular results of write/read). Ok, so when it is obsolete now it can be dropped altogether I guess? cheers, Gerd