qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, samuel.thibault@ens-lyon.org,
	jan.kiszka@siemens.com
Subject: Re: [Qemu-devel] [PATCH v4 4/5] slirp: VMStatify socket level
Date: Thu, 23 Feb 2017 10:51:56 +0000	[thread overview]
Message-ID: <20170223105155.GA2383@work-vm> (raw)
In-Reply-To: <8760k3od2r.fsf@emacs.mitica>

Samual, Jan: Can you just take 1-3 of this series;  4 has a problem;

* Juan Quintela (quintela@redhat.com) wrote:
> "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > Working up the stack, this replaces the slirp_socket_load/save
> > with VMState definitions.
> >
> > A place holder for IPv6 support is added as a comment; it needs
> > testing once the rest of the IPv6 code is there.
> >
> > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> 
> Reviewed-by: Juan Quintela <quintela@redhat.com>
> 
> 
> > +/* Win has a signed family number */
> > +#define VMSTATE_SS_FAMILY(f, s) VMSTATE_INT16(f, s)
> 
> Great!
> Just hope that there is no 32000 families soon :-)

Actually; that's a problem;  it turns out FreeBSD has a char for it's
family type rahter than the uint16 that linux and windows have.
I need to think hth to abstract that.

Dave


> 
> 
> > +#if 0
> > +        /* Untested: Needs checking by someone with IPv6 test */
> > +        VMSTATE_BUFFER_TEST(sin6.sin6_addr, union slirp_sockaddr,
> > +                            slirp_family_inet6),
> > +        VMSTATE_UINT16_TEST(sin6.sin6_port, union slirp_sockaddr,
> > +                            slirp_family_inet6),
> > +        VMSTATE_UINT32_TEST(sin6.sin6_flowinfo, union slirp_sockaddr,
> > +                            slirp_family_inet6),
> > +        VMSTATE_UINT32_TEST(sin6.sin6_scope_id, union slirp_sockaddr,
> > +                            slirp_family_inet6),
> > +#endif
> 
> I think this is wrong, we have different fieldbs depending in if it is
> ipv6 or not?
> 
> Later, Juan.
> 
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  parent reply	other threads:[~2017-02-23 10:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 18:50 [Qemu-devel] [PATCH v4 0/5] SLIRP VMStatification Dr. David Alan Gilbert (git)
2017-02-20 18:50 ` [Qemu-devel] [PATCH v4 1/5] slirp: VMState conversion; tcpcb Dr. David Alan Gilbert (git)
2017-02-20 18:50 ` [Qemu-devel] [PATCH v4 2/5] slirp: VMStatify sbuf Dr. David Alan Gilbert (git)
2017-02-20 18:50 ` [Qemu-devel] [PATCH v4 3/5] slirp: Common lhost/fhost union Dr. David Alan Gilbert (git)
2017-02-20 21:02   ` Philippe Mathieu-Daudé
2017-02-21 13:55   ` Juan Quintela
2017-02-20 18:50 ` [Qemu-devel] [PATCH v4 4/5] slirp: VMStatify socket level Dr. David Alan Gilbert (git)
2017-02-21 14:03   ` Juan Quintela
2017-02-21 14:08     ` Dr. David Alan Gilbert
2017-02-23 10:51     ` Dr. David Alan Gilbert [this message]
2017-02-23 11:04       ` Daniel P. Berrange
2017-02-23 11:40         ` Dr. David Alan Gilbert
2017-02-26 20:34           ` Samuel Thibault
2017-02-26 22:59             ` Samuel Thibault
2017-02-28 16:54             ` Dr. David Alan Gilbert
2017-02-28 16:57               ` Samuel Thibault
2017-02-28 17:00                 ` Dr. David Alan Gilbert
2017-02-28 17:02                   ` Samuel Thibault
2017-02-28 17:09                     ` Dr. David Alan Gilbert
2017-02-28 17:12                       ` Samuel Thibault
2017-02-28 17:40                         ` Dr. David Alan Gilbert
2017-02-28 22:09                           ` Samuel Thibault
2017-02-20 18:50 ` [Qemu-devel] [PATCH v4 5/5] slirp: VMStatify remaining except for loop Dr. David Alan Gilbert (git)
2017-02-21 13:57   ` Juan Quintela
2017-02-20 19:02 ` [Qemu-devel] [PATCH v4 0/5] SLIRP VMStatification no-reply

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=20170223105155.GA2383@work-vm \
    --to=dgilbert@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=samuel.thibault@ens-lyon.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).