From: Peter Maydell <peter.maydell@linaro.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Nabih Estefan <nabihestefan@google.com>,
Hao Wu <wuhaotsh@google.com>
Subject: Re: [PATCH 2/2] tests/qtest/npcm7xx_emc-test: Connect all NICs to a backend
Date: Tue, 6 Feb 2024 17:46:03 +0000 [thread overview]
Message-ID: <CAFEAcA_-opZFSEn4DLGzkpGkoAxJsCpD87SR2Hn3mGMtx-Hy7w@mail.gmail.com> (raw)
In-Reply-To: <bfbeda026f49803025e2a90e41c5e043c93d1a59.camel@infradead.org>
On Tue, 6 Feb 2024 at 17:36, David Woodhouse <dwmw2@infradead.org> wrote:
>
> On Tue, 2024-02-06 at 17:12 +0000, Peter Maydell wrote:
> > Currently QEMU will warn if there is a NIC on the board that
> > is not connected to a backend. By default the '-nic user' will
> > get used for all NICs, but if you manually connect a specific
> > NIC to a specific backend, then the other NICs on the board
> > have no backend and will be warned about:
> >
> > qemu-system-arm: warning: nic npcm7xx-emc.1 has no peer
> > qemu-system-arm: warning: nic npcm-gmac.0 has no peer
> > qemu-system-arm: warning: nic npcm-gmac.1 has no peer
> >
> > So suppress those warnings by manually connecting every NIC
> > on the board to some backend.
> >
> > Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>
> Reviewed-by: David Woodhouse <dwmw@amazon.co.uk>
>
>
> ... although do we want to expand this test to cover the GMACs?
It's very specific to details of how to program the particular
ethernet controller. The GMAC is supposed to be covered by
npcm_gmac-test.c (but that has issues of its own, see
https://lore.kernel.org/qemu-devel/CAFEAcA_gkQz7q+PhiqrVd+YrVJvLt1H=Ypp4av9qn+6mYC6jdA@mail.gmail.com/
and in any case doesn't yet try to actually exercise the device
beyond a rather minimal "check the register reset values"
test that doesn't need any particular backend connected).
thanks
-- PMM
next prev parent reply other threads:[~2024-02-06 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 17:12 [PATCH 0/2] Fix issues with npcm7xx and recent NIC cleanup Peter Maydell
2024-02-06 17:12 ` [PATCH 1/2] hw/arm/npcm7xx: Call qemu_configure_nic_device() for GMAC modules Peter Maydell
2024-02-06 17:36 ` David Woodhouse
2024-02-06 17:12 ` [PATCH 2/2] tests/qtest/npcm7xx_emc-test: Connect all NICs to a backend Peter Maydell
2024-02-06 17:34 ` Peter Maydell
2024-02-06 17:36 ` David Woodhouse
2024-02-06 17:46 ` Peter Maydell [this message]
2024-02-07 7:33 ` Thomas Huth
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=CAFEAcA_-opZFSEn4DLGzkpGkoAxJsCpD87SR2Hn3mGMtx-Hy7w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=dwmw2@infradead.org \
--cc=nabihestefan@google.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wuhaotsh@google.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 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).