From: "Alex Bennée" <alex.bennee@linaro.org>
To: Manolo de Medici <manolodemedici@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, bug-hurd@gnu.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 3/4] Allow tests to be disabled
Date: Wed, 17 Jan 2024 18:40:20 +0000 [thread overview]
Message-ID: <87ttnbhkh7.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAHP40m=pB6aOdoUL36vC=_ku2ynNj6j6n0PC4DkwCgSd5D2OPQ@mail.gmail.com> (Manolo de Medici's message of "Wed, 17 Jan 2024 19:14:02 +0100")
Manolo de Medici <manolodemedici@gmail.com> writes:
> I agree with you, I mentioned that this was the "minimal effort"
> patchset to get qemu compilable.
>
> On Wed, Jan 17, 2024 at 6:35 PM Peter Maydell <peter.maydell@linaro.org> wrote:
> [...]
>> should be guarded by a suitable check that means we don't
>> try to build it on hosts that don't have the host-specific
>> functions/whatever that it needs.
>
> This is the best solution for this problem, any pointers on how to
> best do this?
Look in tests/qtest/meson.build for lines like:
config_all_devices.has_key('CONFIG_TPM_TIS_ISA') ? ['tpm-tis-test'] : [])
It seems we have a bunch of logic for qtests_i386 and qtests_aarch64
which isn't applied to the qtests list. Commenting those out I still get
the full list:
meson test --list | grep tpm
qemu:qtest+qtest-aarch64 / qtest-aarch64/tpm-tis-device-test
qemu:qtest+qtest-aarch64 / qtest-aarch64/tpm-tis-device-swtpm-test
qemu:qtest+qtest-aarch64 / qtest-aarch64/tpm-tis-i2c-test
qemu:qtest+qtest-arm / qtest-arm/tpm-tis-i2c-test
qemu:qtest+qtest-i386 / qtest-i386/tpm-crb-test
qemu:qtest+qtest-i386 / qtest-i386/tpm-crb-swtpm-test
qemu:qtest+qtest-i386 / qtest-i386/tpm-tis-test
qemu:qtest+qtest-i386 / qtest-i386/tpm-tis-swtpm-test
qemu:qtest+qtest-x86_64 / qtest-x86_64/tpm-crb-test
qemu:qtest+qtest-x86_64 / qtest-x86_64/tpm-crb-swtpm-test
qemu:qtest+qtest-x86_64 / qtest-x86_64/tpm-tis-test
qemu:qtest+qtest-x86_64 / qtest-x86_64/tpm-tis-swtpm-test
But I guess there are there to ensure the dependencies are correct so
I'm sure that's not the right fix.
Paolo,
Where is that meant to be done?
>
> Thanks
>
> On Wed, Jan 17, 2024 at 6:35 PM Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> On Wed, 17 Jan 2024 at 12:59, Manolo de Medici <manolodemedici@gmail.com> wrote:
>> >
>> > tests/qtest/tpm-* compilation is not disabled by disable-tpm,
>> > for this reason compilation fails on systems that doesn't
>> > support the linux/bsd TPM api. Fix this by allowing tests
>> > to be disabled.
>>
>> This isn't the right way to fix this. Either the tpm test
>> code has portability issues that can be fixed, or else it
>> should be guarded by a suitable check that means we don't
>> try to build it on hosts that don't have the host-specific
>> functions/whatever that it needs.
>>
>> thanks
>> -- PMM
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2024-01-17 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 12:32 [PATCH 3/4] Allow tests to be disabled Manolo de Medici
2024-01-17 17:35 ` Peter Maydell
2024-01-17 18:14 ` Manolo de Medici
2024-01-17 18:40 ` Alex Bennée [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-17 12:32 Manolo de Medici
2024-01-17 15:09 ` Manolo de Medici
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=87ttnbhkh7.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=bug-hurd@gnu.org \
--cc=manolodemedici@gmail.com \
--cc=pbonzini@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.