From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:33319)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lukego@gmail.com>) id 1UhJKh-0002os-Mz
	for qemu-devel@nongnu.org; Tue, 28 May 2013 08:48:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lukego@gmail.com>) id 1UhJKb-0005gn-30
	for qemu-devel@nongnu.org; Tue, 28 May 2013 08:48:55 -0400
Received: from mail-bk0-x231.google.com ([2a00:1450:4008:c01::231]:48977)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lukego@gmail.com>) id 1UhJKa-0005gf-Sf
	for qemu-devel@nongnu.org; Tue, 28 May 2013 08:48:49 -0400
Received: by mail-bk0-f49.google.com with SMTP id na1so2829610bkb.8
	for <qemu-devel@nongnu.org>; Tue, 28 May 2013 05:48:48 -0700 (PDT)
MIME-Version: 1.0
Sender: lukego@gmail.com
In-Reply-To: <20130528115326.GB21107@redhat.com>
References: <CAA2XHbf4zH-PR827Wwj9z-C-An0+7Ag8_muRS4zsRqVUo7Sb6Q@mail.gmail.com>
	<20130527093409.GH21969@stefanha-thinkpad.redhat.com>
	<CAA2XHbc=+OAAhjMPXDT6+PFVs+uSBN+ZVZHkEPZ-=Q_WtRYG4w@mail.gmail.com>
	<51A496C4.1020602@os.inf.tu-dresden.de>
	<20130528115326.GB21107@redhat.com>
Date: Tue, 28 May 2013 14:48:47 +0200
Message-ID: <CAA2XHbe_RvhCwmqYOgMNi4JSp-QeNtpXBmU-7Fq=rS+jOXjxvg@mail.gmail.com>
From: Luke Gorrie <luke@snabb.co>
Content-Type: multipart/alternative; boundary=bcaec51a743eb5084504ddc6afe5
Subject: Re: [Qemu-devel] [snabb-devel:276] Re: snabbswitch integration with
 QEMU for userspace ethernet I/O
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: "snabb-devel@googlegroups.com" <snabb-devel@googlegroups.com>
Cc: qemu-devel@nongnu.org, Julian Stecklina <jsteckli@os.inf.tu-dresden.de>

--bcaec51a743eb5084504ddc6afe5
Content-Type: text/plain; charset=ISO-8859-1

On 28 May 2013 13:53, Michael S. Tsirkin <mst@redhat.com> wrote:

> Implementing out of process device logic would absolutely be useful for
> qemu, for security.
>

This sounds wonderful from my perspective. The whole PCI device implemented
in my process according to the Virtio spec? What would it take to make this
possible?

I really want snabbswitch <-> guest I/O with as little involvement from
Linux and QEMU as possible.

Personally I can work much more effectively in the snabbswitch code than in
QEMU or Linux and that's why I haven't implemented Stefan's design, despite
having several times sat down with the intention of doing so :)

--bcaec51a743eb5084504ddc6afe5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">On 28 May 2013 13:53, Michael S=
. Tsirkin <span dir=3D"ltr">&lt;<a href=3D"mailto:mst@redhat.com" target=3D=
"_blank">mst@redhat.com</a>&gt;</span> wrote:<br><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
<div class=3D"HOEnZb"><div class=3D"h5">Implementing out of process device =
logic would absolutely be useful for<br></div></div>
qemu, for security.<br></blockquote><div><br></div><div style>This sounds w=
onderful from my perspective. The whole PCI device implemented in my proces=
s according to the Virtio spec? What would it take to make this possible?</=
div>
<div style><br></div><div style>I really want snabbswitch &lt;-&gt; guest I=
/O with as little involvement from Linux and QEMU as possible.=A0</div><div=
 style><br></div><div style>Personally I can work much more effectively in =
the snabbswitch code than in QEMU or Linux and that&#39;s why I haven&#39;t=
 implemented Stefan&#39;s design, despite having several times sat down wit=
h the intention of doing so :)</div>
<div style><br></div><div style><br></div></div></div></div>

--bcaec51a743eb5084504ddc6afe5--