From: Markus Armbruster <armbru@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org, "Eric Blake" <eblake@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Stefano Brivio" <sbrivio@redhat.com>
Subject: Re: [PATCH v5 05/12] qapi: net: add stream and dgram netdevs
Date: Wed, 29 Jun 2022 15:49:47 +0200 [thread overview]
Message-ID: <8735fneg04.fsf@pond.sub.org> (raw)
In-Reply-To: <20220627154749.871943-6-lvivier@redhat.com> (Laurent Vivier's message of "Mon, 27 Jun 2022 17:47:42 +0200")
Laurent Vivier <lvivier@redhat.com> writes:
> Copied from socket netdev file and modified to use SocketAddress
> to be able to introduce new features like unix socket.
>
> "udp" and "mcast" are squashed into dgram netdev, multicast is detected
> according to the IP address type.
> "listen" and "connect" modes are managed by stream netdev. An optional
> parameter "server" defines the mode (server by default)
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> Reviewed-by: Stefano Brivio <sbrivio@redhat.com>
Suggest to add a summary of what we learned during review. Let me try.
The two new types need to parsed the modern way with -netdev, because
<explanation goes here>.
The previous commit paved the way for parsing the modern way, but
omitted one detail: how to pick modern vs. traditional, in
netdev_is_modern().
We want to pick based on the value of parameter "type". But how to
extract it from the option argument?
Parsing the option argument, either the modern or the traditional way,
extracts it for us, but only if parsing succeeds.
If parsing fails, there is no good option. No matter which parser we
pick, it'll be the wrong one for some arguments, and the error
reporting will be confusing.
Fortunately, the traditional parser accepts *anything* when called in
a certain way. This maximizes our chance to extract the value of
"type", and in turn minimizes the risk of confusing error reporting.
How do you like it?
next prev parent reply other threads:[~2022-06-29 13:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 15:47 [PATCH v5 00/12] qapi: net: add unix socket type support to netdev backend Laurent Vivier
2022-06-27 15:47 ` [PATCH v5 01/12] net: introduce convert_host_port() Laurent Vivier
2022-06-27 15:47 ` [PATCH v5 02/12] net: remove the @errp argument of net_client_inits() Laurent Vivier
2022-06-27 15:47 ` [PATCH v5 03/12] net: simplify net_client_parse() error management Laurent Vivier
2022-06-29 10:50 ` Markus Armbruster
2022-06-27 15:47 ` [PATCH v5 04/12] qapi: net: introduce a way to bypass qemu_opts_parse_noisily() Laurent Vivier
2022-06-29 13:21 ` Markus Armbruster
2022-06-27 15:47 ` [PATCH v5 05/12] qapi: net: add stream and dgram netdevs Laurent Vivier
2022-06-29 11:20 ` Markus Armbruster
2022-06-30 15:09 ` Laurent Vivier
2022-06-29 13:49 ` Markus Armbruster [this message]
2022-06-27 15:47 ` [PATCH v5 06/12] net: stream: Don't ignore EINVAL on netdev socket connection Laurent Vivier
2022-06-27 15:47 ` [PATCH v5 07/12] net: stream: add unix socket Laurent Vivier
2022-06-30 9:28 ` Dr. David Alan Gilbert
2022-07-01 9:20 ` Laurent Vivier
2022-07-04 5:12 ` Markus Armbruster
2022-06-27 15:47 ` [PATCH v5 08/12] net: dgram: make dgram_dst generic Laurent Vivier
2022-06-27 15:47 ` [PATCH v5 09/12] net: dgram: move mcast specific code from net_socket_fd_init_dgram() Laurent Vivier
2022-06-27 15:47 ` [PATCH v5 10/12] net: dgram: add unix socket Laurent Vivier
2022-06-27 15:47 ` [PATCH v5 11/12] qemu-sockets: introduce socket_uri() Laurent Vivier
2022-06-30 9:35 ` Dr. David Alan Gilbert
2022-06-27 15:47 ` [PATCH v5 12/12] net: stream: move to QIO Laurent Vivier
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=8735fneg04.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=jasowang@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sbrivio@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.