From: Samuel Thibault <samuel.thibault@gnu.org>
To: marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH slirp 4/5] slirp: add state saving/loading
Date: Sat, 9 Feb 2019 12:40:41 +0100 [thread overview]
Message-ID: <20190209114041.ibd3adln5vw4iky5@function> (raw)
In-Reply-To: <20190208181122.23393-5-marcandre.lureau@redhat.com>
marcandre.lureau@redhat.com, le ven. 08 févr. 2019 19:11:21 +0100, a ecrit:
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> Based on qemu vmstate serialization code. At this point it should
> produce the same result. However, with future state versions, slirp
> should be free to change its format, by bumping the reported state
> version.
Mmm, then qemu needs to be taught to call slirp_state_save/load/version?
Samuel
next prev parent reply other threads:[~2019-02-09 11:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 18:11 [Qemu-devel] [PATCH slirp 0/5] Make it a standalone project marcandre.lureau
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 1/5] Extract slirp/ from qemu repository marcandre.lureau
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 2/5] build-sys: add a meson build marcandre.lureau
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 3/5] build-sys: add version tooling marcandre.lureau
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 4/5] slirp: add state saving/loading marcandre.lureau
2019-02-09 11:40 ` Samuel Thibault [this message]
2019-02-09 13:09 ` Marc-André Lureau
2019-02-09 13:12 ` Samuel Thibault
2019-02-09 13:16 ` Marc-André Lureau
2019-02-09 13:19 ` Samuel Thibault
2019-02-08 18:11 ` [Qemu-devel] [PATCH slirp 5/5] Add .gitlab-ci.yml marcandre.lureau
2019-02-09 11:33 ` [Qemu-devel] [PATCH slirp 0/5] Make it a standalone project Samuel Thibault
2019-02-10 21:35 ` Peter Maydell
2019-02-10 21:38 ` Samuel Thibault
2019-02-10 21:42 ` Peter Maydell
2019-02-10 22:03 ` Marc-André Lureau
2019-02-10 22:07 ` Peter Maydell
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=20190209114041.ibd3adln5vw4iky5@function \
--to=samuel.thibault@gnu.org \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).