From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:34743) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TaTmV-0001MK-Fn for qemu-devel@nongnu.org; Mon, 19 Nov 2012 11:01:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TaTmO-000715-5o for qemu-devel@nongnu.org; Mon, 19 Nov 2012 11:01:07 -0500 Received: from mail-vc0-f173.google.com ([209.85.220.173]:44166) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TaTmN-00070P-W7 for qemu-devel@nongnu.org; Mon, 19 Nov 2012 11:01:00 -0500 Received: by mail-vc0-f173.google.com with SMTP id fl15so5115279vcb.4 for ; Mon, 19 Nov 2012 08:00:59 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20121119085528.GD17444@stefanha-thinkpad.redhat.com> References: <20121119085528.GD17444@stefanha-thinkpad.redhat.com> Date: Mon, 19 Nov 2012 17:00:58 +0100 Message-ID: From: lementec fabien Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Qemu-devel] TCP based PCIE request forwarding List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Cam Macdonell , Nick Gasson , qemu-devel , fred.konrad@greensocs.com Hi, Thanks, it is actually a good idea to start with. I will write a spec based on an improved version of what I have already implemented. I think I will have some time this week, I will keep you updated soon. Best regards, Fabien. 2012/11/19 Stefan Hajnoczi : > On Fri, Nov 16, 2012 at 02:05:29PM +0100, lementec fabien wrote: >> Actually, I wanted to be independant of the QEMU event loop. Plus, >> some proprietary simulation environment provides a closed socket >> based interface to 'stimulate' the emulated device, at the PCIE level >> for instance. These environments are sometimes installed on cluster >> not running QEMU. The socket based approach fits quite well. >> >> Not knowing about QEMU internals, I spent some hours trying to find >> out the best way to plug into QEMU, and did not find ivhsmem appropriate. >> Honestly, I wanted to have a working solution asap, and it did not take >> long before I opted for the socket based approach. Now that it is working, >> I can take time to reconsider stuffs according to others need, and ideally >> an integration to QEMU. > > I suggest writing up a spec for the socket protocol. It can be put in > docs/specs/ (like the ivshmem spec). > > This is both a good way to increase discussion and important for others > who may wish to make use of this feature. > > Stefan