From: Samuel Thibault <samuel.thibault@gnu.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: renzo@cs.unibo.it, virtualsquare@cs.unibo.it, thuth@redhat.com,
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: Wed, 8 Feb 2017 23:10:50 +0100 [thread overview]
Message-ID: <20170208221050.GP2955@var.home> (raw)
In-Reply-To: <CAJSP0QWT14J-cqwLqPCr0iC95pSLaiZJgPkqr1VBU=pqYF6kqQ@mail.gmail.com>
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 :)
Personally, I'm fine with seeing slirp move to a separate playground
that qemu would depend on and others could contribute to. It just needs
to be integrated to distros so that qemu can get it.
That being said, the integration of slirp and qemu is not so loose,
notably on the top of my head:
- we are using timers for icmp announcements
- qemu needs to be able to save/restore state, with compatibility with
previous versions
We'd need to see how that can be expressed as a library.
Samuel
next prev parent reply other threads:[~2017-02-08 22:10 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 [this message]
2017-02-12 7:30 ` Renzo Davoli
2017-02-13 10:56 ` Thomas Huth
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=20170208221050.GP2955@var.home \
--to=samuel.thibault@gnu.org \
--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=stefanha@gmail.com \
--cc=thuth@redhat.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).