From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56888) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b9oR2-0001KA-Bh for qemu-devel@nongnu.org; Mon, 06 Jun 2016 02:54:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b9oQy-0003XE-6q for qemu-devel@nongnu.org; Mon, 06 Jun 2016 02:54:51 -0400 Received: from mx1.redhat.com ([209.132.183.28]:39785) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b9oQy-0003X7-1q for qemu-devel@nongnu.org; Mon, 06 Jun 2016 02:54:48 -0400 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6C755C06C9CB for ; Mon, 6 Jun 2016 06:54:47 +0000 (UTC) Message-ID: <1465196085.24775.185.camel@redhat.com> From: Gerd Hoffmann Date: Mon, 06 Jun 2016 08:54:45 +0200 In-Reply-To: <1465076003-26291-15-git-send-email-marcandre.lureau@redhat.com> References: <1465076003-26291-1-git-send-email-marcandre.lureau@redhat.com> <1465076003-26291-15-git-send-email-marcandre.lureau@redhat.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 Subject: Re: [Qemu-devel] [RFC 14/14] Add virtio-gpu vhost-user backend List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: marcandre.lureau@redhat.com Cc: qemu-devel@nongnu.org On Sa, 2016-06-04 at 23:33 +0200, marcandre.lureau@redhat.com wrote: > From: Marc-Andr=C3=A9 Lureau >=20 > Add to virtio-gpu devices a "vhost-user" property. When set, the > associated vhost-user backend is used to handle the virtio rings. >=20 > For now, a socketpair is created for the backend to share the rendering > results with qemu via a simple VHOST_GPU protocol. Can you give a design overview? On a first look this seems to not share much code with virtio-gpu either, so I guess it makes sense to put this into a separate virtio-gpu-vhost device too. cheers, Gerd