From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-ppc@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
qemu-arm@nongnu.org, qemu-block@nongnu.org,
"Laurent Vivier" <lvivier@redhat.com>
Subject: Re: [PATCH 1/4] tests/libqtest: Introduce qtest_get_arch_bits()
Date: Tue, 10 Oct 2023 11:46:24 +0200 [thread overview]
Message-ID: <e108d282-5eec-4430-1a10-8cf3170bb18c@redhat.com> (raw)
In-Reply-To: <20231010074952.79165-2-philmd@linaro.org>
On 10/10/2023 09.49, Philippe Mathieu-Daudé wrote:
> Add a method to return the architecture bits (currently 8/32/64).
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> tests/qtest/libqtest.h | 8 ++++++++
> tests/qtest/libqtest.c | 21 +++++++++++++++++++++
> 2 files changed, 29 insertions(+)
>
> diff --git a/tests/qtest/libqtest.h b/tests/qtest/libqtest.h
> index e53e350e3a..1e1b42241d 100644
> --- a/tests/qtest/libqtest.h
> +++ b/tests/qtest/libqtest.h
> @@ -654,6 +654,14 @@ bool qtest_big_endian(QTestState *s);
> */
> const char *qtest_get_arch(void);
>
> +/**
> + * qtest_get_arch_bits:
> + *
> + * Returns: The architecture bits (a.k.a. word size) for the QEMU executable
> + * under test.
> + */
> +unsigned qtest_get_arch_bits(void);
> +
> /**
> * qtest_has_accel:
> * @accel_name: Accelerator name to check for.
> diff --git a/tests/qtest/libqtest.c b/tests/qtest/libqtest.c
> index b1eba71ffe..a643a6309c 100644
> --- a/tests/qtest/libqtest.c
> +++ b/tests/qtest/libqtest.c
> @@ -925,6 +925,27 @@ const char *qtest_get_arch(void)
> return end + 1;
> }
>
> +unsigned qtest_get_arch_bits(void)
> +{
> + static const char *const arch64[] = {
> + "aarch64", "hppa", "x86_64", "loongarch64", "mips64",
> + "mips64el", "ppc64", "riscv64", "s390x", "sparc64",
> + };
> + const char *arch = qtest_get_arch();
> +
> + if (!strcmp(arch, "avr")) {
Just a matter of taste, but I prefer g_str_equal(), that's easier to read.
> + return 8;
> + }
> +
> + for (unsigned i = 0; i < ARRAY_SIZE(arch64); i++) {
> + if (!strcmp(arch, arch64[i])) {
> + return 64;
> + }
> + }
> +
> + return 32;
> +}
Since this function might get called multiple times, would it make sense to
cache the value? I.e.:
static const unsigned bits;
if (!bits) {
... do all the magic to find out the right bits ...
}
return bits;
?
Thomas
next prev parent reply other threads:[~2023-10-10 9:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 7:49 [PATCH 0/4] tests/qtest: Introduce qtest_get_base_arch() and qtest_get_arch_bits() Philippe Mathieu-Daudé
2023-10-10 7:49 ` [PATCH 1/4] tests/libqtest: Introduce qtest_get_arch_bits() Philippe Mathieu-Daudé
2023-10-10 9:46 ` Thomas Huth [this message]
2023-10-10 9:48 ` Philippe Mathieu-Daudé
2023-10-10 7:49 ` [PATCH 2/4] tests/qtest: Use qtest_get_arch_bits() Philippe Mathieu-Daudé
2023-10-10 9:49 ` Thomas Huth
2023-10-10 10:03 ` Ani Sinha
2023-10-10 7:49 ` [PATCH 3/4] tests/libqtest: Introduce qtest_get_base_arch() Philippe Mathieu-Daudé
2023-10-10 8:42 ` Philippe Mathieu-Daudé
2023-10-10 9:50 ` Thomas Huth
2023-10-10 7:49 ` [PATCH 4/4] tests/qtest: Use qtest_get_base_arch() Philippe Mathieu-Daudé
2023-10-10 9:38 ` Akihiko Odaki
2023-10-10 9:58 ` Thomas Huth
2023-10-10 10:37 ` Philippe Mathieu-Daudé
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=e108d282-5eec-4430-1a10-8cf3170bb18c@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).