From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] net: Silence 'has no peer' messages in testing mode
Date: Tue, 8 May 2018 15:19:24 +0200 [thread overview]
Message-ID: <9d66d071-324f-5d33-547d-901f497cb497@redhat.com> (raw)
In-Reply-To: <87in80ym1o.fsf@dusky.pond.sub.org>
On 07.05.2018 09:14, Markus Armbruster wrote:
[...]
> Two (possibly confused) questions:
>
> 1. The user can add nics without convenience options:
>
> $ upstream-qemu -display none -nodefaults -device e1000
> upstream-qemu: warning: nic e1000.0 has no peer
>
> Shouldn't we silence the warning then, too?
No, since that is certainly a mis-configuration in that case. Why would
a user want to add a NIC without host backend?
> 2. We already have code to silence the warning:
>
> /* Don't warn about the default network setup that you get if
> * no command line -net or -netdev options are specified. There
> * are two cases that we would otherwise complain about:
> * (1) board doesn't support a NIC but the implicit "-net nic"
> * requested one
> * (2) CONFIG_SLIRP not set, in which case the implicit "-net nic"
> * sets up a nic that isn't connected to anything.
> */
> if (!default_net) {
> net_check_clients();
> }
>
> Is it a good idea to split the logic between net_check_clients() and
> its caller?
Hmm, it's likely nicer to keep everything in one place. Since
"default_net" is only available in vl.c, I think the checks should go
there... so I'll rework my patch accordingly.
Thomas
next prev parent reply other threads:[~2018-05-08 13:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 5:50 [Qemu-devel] [PATCH] net: Silence 'has no peer' messages in testing mode Thomas Huth
2018-05-03 11:47 ` Markus Armbruster
2018-05-04 14:55 ` Thomas Huth
2018-05-07 7:14 ` Markus Armbruster
2018-05-08 13:19 ` Thomas Huth [this message]
2018-05-09 6:18 ` Markus Armbruster
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=9d66d071-324f-5d33-547d-901f497cb497@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=jasowang@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).