From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:34765)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1TaN8g-00029Q-JC
	for qemu-devel@nongnu.org; Mon, 19 Nov 2012 03:55:37 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1TaN8d-0007LQ-GZ
	for qemu-devel@nongnu.org; Mon, 19 Nov 2012 03:55:34 -0500
Received: from mail-bk0-f45.google.com ([209.85.214.45]:64194)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@gmail.com>) id 1TaN8d-0007LJ-8V
	for qemu-devel@nongnu.org; Mon, 19 Nov 2012 03:55:31 -0500
Received: by mail-bk0-f45.google.com with SMTP id jk13so791371bkc.4
	for <qemu-devel@nongnu.org>; Mon, 19 Nov 2012 00:55:30 -0800 (PST)
Date: Mon, 19 Nov 2012 09:55:28 +0100
From: Stefan Hajnoczi <stefanha@gmail.com>
Message-ID: <20121119085528.GD17444@stefanha-thinkpad.redhat.com>
References: <CAAPMK-T4pmMr+SR8miDzDtLuGtS+5Q6yqJk4C80M8PAX21gYKA@mail.gmail.com>
	<CAJSP0QU6T3=7fzLXgmbuoTWtxN1vxWtLEu1KupocNZHX-Pvqeg@mail.gmail.com>
	<CAAPMK-RyEYYsVVtV2PJnhuvkfzsGrJkzcsQYLocShFDU=QP+Ng@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAPMK-RyEYYsVVtV2PJnhuvkfzsGrJkzcsQYLocShFDU=QP+Ng@mail.gmail.com>
Subject: Re: [Qemu-devel] TCP based PCIE request forwarding
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: lementec fabien <fabien.lementec@gmail.com>
Cc: Cam Macdonell <cam@cs.ualberta.ca>, Nick Gasson <nick@nickg.me.uk>, qemu-devel <qemu-devel@nongnu.org>, fred.konrad@greensocs.com

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