From: Eric Auger <eric.auger@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: lvivier@redhat.com, peter.maydell@linaro.org, thuth@redhat.com,
f4bug@amsat.org, qemu-devel@nongnu.org, qemu-arm@nongnu.org,
pbonzini@redhat.com, eric.auger.pro@gmail.com
Subject: Re: [PATCH 2/2] tests/qtest: Special case sbsa-ref and xlnx-versal-virt if !CONFIG_ARM_GIC_TCG
Date: Mon, 31 Jan 2022 17:15:48 +0100 [thread overview]
Message-ID: <ba89bcc9-417b-c373-d11d-365675e90414@redhat.com> (raw)
In-Reply-To: <20220131155936.lm7jn32ihb2ndsf7@gator>
Hi Drew,
On 1/31/22 4:59 PM, Andrew Jones wrote:
> On Mon, Jan 31, 2022 at 04:45:31PM +0100, Eric Auger wrote:
>> qom-test and test-hmp shall not run tests on sbsa-ref and
>> xlnx-versal-virt if CONFIG_ARM_GIC_TCG is unset as those machines
>> always instantiate GICv3.
>>
>> Otherwise the tests fail with
>> ERROR:../qom/object.c:715:object_new_with_type: assertion failed: (type != NULL)
>>
>> Signed-off-by: Eric Auger <eric.auger@redhat.com>
>> Fixes: a8a5546798c3 ("hw/intc/arm_gicv3: Introduce CONFIG_ARM_GIC_TCG Kconfig selector")
>> ---
>> tests/qtest/libqtest.c | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/tests/qtest/libqtest.c b/tests/qtest/libqtest.c
>> index 41f4da4e54..f53983a28e 100644
>> --- a/tests/qtest/libqtest.c
>> +++ b/tests/qtest/libqtest.c
>> @@ -1394,6 +1394,12 @@ void qtest_cb_for_every_machine(void (*cb)(const char *machine),
>> g_str_equal("xenpv", machines[i].name)) {
>> continue;
>> }
>> +#ifndef CONFIG_ARM_GIC_TCG
>> + if (!strncmp("sbsa-ref", machines[i].name, 8) ||
>> + !strncmp("xlnx-versal-virt", machines[i].name, 16)) {
>> + continue;
>> + }
>> +#endif
> Hmm, if these machine types completely depend on userspace gicv3
> emulation, i.e. no way to use in-kernel gic or another tcg gic
> model, then I guess they shouldn't be built at all when ARM_GIC_TCG
> isn't configured. I.e.
Yes your suggestion make sense to me, thatw would be a better fix indeed.
Eric
>
> diff --git a/hw/arm/Kconfig b/hw/arm/Kconfig
> index 2e0049196d6c..d7cc028b049d 100644
> --- a/hw/arm/Kconfig
> +++ b/hw/arm/Kconfig
> @@ -209,6 +209,7 @@ config REALVIEW
>
> config SBSA_REF
> bool
> + depends on ARM_GIC_TCG
> imply PCI_DEVICES
> select AHCI
> select ARM_SMMUV3
> @@ -378,6 +379,7 @@ config XLNX_ZYNQMP_ARM
>
> config XLNX_VERSAL
> bool
> + depends on ARM_GIC_TCG
> select ARM_GIC
> select PL011
> select CADENCE
>
>
> Thanks,
> drew
>
>> if (!skip_old_versioned ||
>> !qtest_is_old_versioned_machine(machines[i].name)) {
>> cb(machines[i].name);
>> --
>> 2.26.3
>>
prev parent reply other threads:[~2022-01-31 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 15:45 [PATCH 0/2] hw/arm/virt, qtests: Fix make check-qtest-aarch64 when CONFIG_ARM_GIC_TCG is unset Eric Auger
2022-01-31 15:45 ` [PATCH 1/2] hw/arm/virt: Fix gic-version=max " Eric Auger
2022-01-31 15:53 ` Andrew Jones
2022-01-31 15:45 ` [PATCH 2/2] tests/qtest: Special case sbsa-ref and xlnx-versal-virt if !CONFIG_ARM_GIC_TCG Eric Auger
2022-01-31 15:59 ` Andrew Jones
2022-01-31 16:05 ` Peter Maydell
2022-01-31 16:14 ` Andrew Jones
2022-01-31 16:18 ` Peter Maydell
2022-01-31 16:18 ` Eric Auger
2022-01-31 16:15 ` Eric Auger [this message]
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=ba89bcc9-417b-c373-d11d-365675e90414@redhat.com \
--to=eric.auger@redhat.com \
--cc=drjones@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=f4bug@amsat.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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).