From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43346) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1Cwp-0005bA-RG for qemu-devel@nongnu.org; Tue, 24 Nov 2015 07:43:52 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a1Cwl-0008JI-RN for qemu-devel@nongnu.org; Tue, 24 Nov 2015 07:43:51 -0500 Received: from mx1.redhat.com ([209.132.183.28]:41576) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1Cwl-0008JA-Mw for qemu-devel@nongnu.org; Tue, 24 Nov 2015 07:43:47 -0500 References: <871tbktuzy.fsf@blackfin.pond.sub.org> <565321D9.7080604@redhat.com> <8737vv60sn.fsf_-_@blackfin.pond.sub.org> From: Paolo Bonzini Message-ID: <56545B80.20905@redhat.com> Date: Tue, 24 Nov 2015 13:43:44 +0100 MIME-Version: 1.0 In-Reply-To: <8737vv60sn.fsf_-_@blackfin.pond.sub.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Is ivshmem's use of qemu_chr_open_eventfd() kosher? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: marcandre.lureau@redhat.com, Claudio Fontana , qemu-devel@nongnu.org, Luiz Capitulino On 24/11/2015 13:26, Markus Armbruster wrote: > Device models (a.k.a. frontends) are normally not supposed to create > backends by themselves, because it blurs the separation between frontend > and backend, and commonly denies the user the opportunity to fully > configure the backend. Right, but here the fd comes from the ivshmem server. It's just using the chardev API internally. It could be changed with little effort to use a GSource or qemu_set_fd_handler. Paolo