qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "patches@linaro.org" <patches@linaro.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] net: reimplement -net nic diagnostic fix
Date: Fri, 20 May 2011 18:07:56 +0200	[thread overview]
Message-ID: <4DD691DC.7080109@siemens.com> (raw)
In-Reply-To: <BANLkTi=Er1_cVt7RugRmL-LrW23HN0qQ3Q@mail.gmail.com>

On 2011-05-20 18:04, Peter Maydell wrote:
> On 20 May 2011 16:55, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> On 2011-05-20 17:49, Peter Maydell wrote:
>>> This patchset reverts commit f68b9d672, which was triggering
>>> spuriously for NICs created via -device rather than -net nic.
>>> It then reimplements the improved diagnostics with a different
>>> approach which only applies to '-net nic'. (It's only -net nic
>>> devices that can be ignored (ie not instantiated); -device
>>> nic devices are always instantiated. Checking for -device user
>>> errors like "this device wasn't plugged into any bus" is
>>> a separate issue not addressed here.)
>>
>> But we still have the problem that qemu_new_nic does not call
>> net_init_nic. That means e.g. that NICs instantiated via -device don't
>> participate in automatic MAC assignment. Maybe fixing that makes this
>> series obsolete.
> 
> I think that avoiding MAC address clashes should be done by
> having net_init_nic() call qemu_macaddr_default_if_unset()

You mean qemu_new_nic? Otherwise it wouldn't help. Will have a look to
move that over.

> rather than doing its own MAC assignment.
> 
> Having qemu_new_nic() call net_init_nic() is a bit tricky
> because (a) as you said earlier you need to avoid doing
> it for NICs which were created from nd_table entries in the
> first place and (b) it imposes a new limit on the number
> of NICs you can create via -device which wasn't there before
> (because nd_table is fixed size).
> 
> I think I agree with Paul Brook's comment on IRC that the
> real long term solution is for nd_table[] to go away completely,
> (ie not for the new qdev option code to add entries in nd_table[]
> by calling net_init_nic().)

I don't disagree that nd_table is better removed. Then let's address all
those issues separately.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-05-20 16:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 15:49 [Qemu-devel] [PATCH 0/3] net: reimplement -net nic diagnostic fix Peter Maydell
2011-05-20 15:49 ` [Qemu-devel] [PATCH 1/3] Revert "net: Improve the warnings for dubious command line option combinations" Peter Maydell
2011-05-20 15:50 ` [Qemu-devel] [PATCH 2/3] net: Don't warn about the default network setup Peter Maydell
2011-05-23  8:30   ` Markus Armbruster
2011-05-23  8:55     ` Peter Maydell
2011-05-20 15:50 ` [Qemu-devel] [PATCH 3/3] net: Warn about "-net nic" options which were ignored Peter Maydell
2011-05-23  8:34   ` Markus Armbruster
2011-05-20 15:55 ` [Qemu-devel] [PATCH 0/3] net: reimplement -net nic diagnostic fix Jan Kiszka
2011-05-20 16:04   ` Peter Maydell
2011-05-20 16:07     ` Jan Kiszka [this message]
2011-05-20 16:12       ` Peter Maydell
2011-05-20 16:15         ` Jan Kiszka
2011-05-23  8:35 ` Markus Armbruster
2011-06-05 13:12 ` Peter Maydell
2011-06-22 11:39   ` Peter Maydell
2011-06-22 12:58 ` Anthony Liguori

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=4DD691DC.7080109@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=armbru@redhat.com \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --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).