From: Thomas Huth <thuth@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [PATCH] tests/qtest: Fix boot-serial-test when using --without-default-devices
Date: Mon, 19 Feb 2024 13:30:46 +0100 [thread overview]
Message-ID: <359e3bf6-bd94-42e5-b8e7-06b41805fd03@redhat.com> (raw)
In-Reply-To: <b56a11d4-ef54-64ae-76ef-25c600255b59@eik.bme.hu>
On 19/02/2024 12.37, BALATON Zoltan wrote:
> On Mon, 19 Feb 2024, Thomas Huth wrote:
>> If "configure" has been run with "--without-default-devices", there is
>> no e1000 device in the binaries, so the boot-serial-test currently fails
>> in that case since it tries to use the e1000 with the sam460ex machine.
>>
>> Since we're testing the serial output here, and not the NIC, let's
>> simply switch to the "pci-bridge" device here instead, which should
>> always be there for PCIe-based machines like the sam460ex.
>
> It's not actually testing PCIe but PCI bus but I think that does not matter.
> PCIe on sam460ex does not work yet, I've only implemented it partially to
> pass the firmware init but devices attached to the PCIe bus probably won't
> work. I have some patches to improve that but not yet ready.
Ah, ok, I looked at the Kconfig file and saw the "select PCI_EXPRESS" there
that got selected by PPC440 (which gets selected by SAM460EX), that's why I
concluded that it must be "PCIe-based" ... I'll drop the "e" here.
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> tests/qtest/boot-serial-test.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tests/qtest/boot-serial-test.c b/tests/qtest/boot-serial-test.c
>> index 6dd06aeaf4..e3b7d65fe5 100644
>> --- a/tests/qtest/boot-serial-test.c
>> +++ b/tests/qtest/boot-serial-test.c
>> @@ -156,7 +156,7 @@ static const testdef_t tests[] = {
>> "Open Firmware" },
>> { "ppc64", "powernv8", "", "OPAL" },
>> { "ppc64", "powernv9", "", "OPAL" },
>> - { "ppc64", "sam460ex", "-device e1000", "8086 100e" },
>> + { "ppc64", "sam460ex", "-device pci-bridge,chassis_nr=2", "1b36
>> 0001" },
>
> So if you want to check if PCI bus works then maybe there's no need to add a
> device at all just look for the sm501 display chip ("126f 0501") that's
> soldered on the board so it's always created even with -nodefaults and
> should always present on sam460ex. The -device option just adds a device
> that appears before the sm501 and stops the test there. Not sure if this is
> testing more than looking for a PCI device created by the board code.
I was considering the sm501, too, but I thought that we might test a little
bit more if we check that cold-plugging via "-device" works, too, so I'd
prefer to keep it this way.
Thomas
next prev parent reply other threads:[~2024-02-19 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 11:10 [PATCH] tests/qtest: Fix boot-serial-test when using --without-default-devices Thomas Huth
2024-02-19 11:37 ` BALATON Zoltan
2024-02-19 12:30 ` Thomas Huth [this message]
2024-02-19 13:14 ` BALATON Zoltan
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=359e3bf6-bd94-42e5-b8e7-06b41805fd03@redhat.com \
--to=thuth@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-trivial@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).