qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Ani Sinha <anisinha@redhat.com>, Thomas Huth <thuth@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: "Reviewed-by : Daniel P . Berrangé" <berrange@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v2 2/3] tests/qtest/libqtest: add qtest_has_cpu() api
Date: Mon, 10 Jun 2024 16:38:46 +0200	[thread overview]
Message-ID: <f4812da5-8c1c-454b-b571-35bba37b8098@linaro.org> (raw)
In-Reply-To: <20240610132123.6381-1-anisinha@redhat.com>

Hi Ani,

On 10/6/24 15:21, Ani Sinha wrote:
> Added a new test api qtest_has_cpu() in order to check availability of some
> cpu models in the current QEMU binary. The specific architecture of the QEMU
> binary is selected using the QTEST_QEMU_BINARY environment variable. This api
> would be useful to run tests against some older cpu models after checking if
> QEMU actually supported these models.
> 
> CC: thuth@redhat.com
> Signed-off-by: Ani Sinha <anisinha@redhat.com>
> Reviewed-by: Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
>   tests/qtest/libqtest.c | 83 ++++++++++++++++++++++++++++++++++++++++++
>   tests/qtest/libqtest.h |  8 ++++
>   2 files changed, 91 insertions(+)

Since "CPU" commonly refers to a CPU state, I suggest renaming as:

> +struct CpuInfo {

CpuModel

> +static struct CpuInfo *qtest_get_cpus(void)

qtest_get_cpu_models()

> +bool qtest_has_cpu(const char *cpu)

qtest_has_cpu_model()

Regards,

Phil.


      reply	other threads:[~2024-06-10 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 13:21 [PATCH v2 2/3] tests/qtest/libqtest: add qtest_has_cpu() api Ani Sinha
2024-06-10 14:38 ` Philippe Mathieu-Daudé [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=f4812da5-8c1c-454b-b571-35bba37b8098@linaro.org \
    --to=philmd@linaro.org \
    --cc=anisinha@redhat.com \
    --cc=berrange@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).