From: Thomas Huth <thuth@redhat.com>
To: Renzo Davoli <renzo@cs.unibo.it>,
Samuel Thibault <samuel.thibault@gnu.org>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
virtualsquare@cs.unibo.it, jasowang@redhat.com,
Jan Kiszka <jan.kiszka@web.de>,
peter.maydell@linaro.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] libslirp and QEMU slirp
Date: Mon, 13 Feb 2017 11:56:11 +0100 [thread overview]
Message-ID: <a4a3f167-b23b-621c-3d69-5fe32f7df239@redhat.com> (raw)
In-Reply-To: <20170212073019.GA25566@cs.unibo.it>
On 12.02.2017 08:30, Renzo Davoli wrote:
> Hi,
>
> On Wed, Feb 08, 2017 at 11:10:50PM +0100, Samuel Thibault wrote:
>> Hello,
>>
>> Stefan Hajnoczi, on Mon 06 Feb 2017 11:55:05 +0000, wrote:
>>> I'm proposing this topic for discussion because there might be common
>>> ground for Samuel from QEMU and the VDE folks to collaborate.
>>>
>>> Samuel: Should QEMU join forces with libslirp?
>>
>> Well, there are not that many forces from the QEMU side :)
> Neither on VDE side ;-) but many ants can move mountains...
>>
>> - we are using timers for icmp announcements
>> - qemu needs to be able to save/restore state, with compatibility with
>> previous versions
>
> libslirp is using qemu's slirp code.
[...]
> Timers have been reimplemented using the qemu's API.
> save/restore are dummy stubs in libslirp. Qemu's code is still there but it is not used
> by libslirp.
Well, sure, but if this libslirp is going to evolve into a
QEMU-independent library, such timer and save/restore hacks likely
should go away from the library and implemented on the side of the
consuming application instead.
> It would be a nice project to create a common codebase for libslirp.
> The project sould be interesting for other VM projects (virtualbox-OSE?) and
> maybe many others. We could collect several ants...
FWIW, I know that WinUAE is using QEMU's slirp code, too.
I've got a question: Is there already a project page and public
repository for libslirp available somewhere? I did not find anything
useful with Google yet...
Thomas
next prev parent reply other threads:[~2017-02-13 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 11:55 [Qemu-devel] libslirp and QEMU slirp Stefan Hajnoczi
2017-02-08 22:10 ` Samuel Thibault
2017-02-12 7:30 ` Renzo Davoli
2017-02-13 10:56 ` Thomas Huth [this message]
2017-02-13 11:21 ` Renzo Davoli
2017-02-15 14:33 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4a3f167-b23b-621c-3d69-5fe32f7df239@redhat.com \
--to=thuth@redhat.com \
--cc=jan.kiszka@web.de \
--cc=jasowang@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=renzo@cs.unibo.it \
--cc=samuel.thibault@gnu.org \
--cc=stefanha@gmail.com \
--cc=virtualsquare@cs.unibo.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).