From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Juan Quintela" <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
qemu-arm@nongnu.org, "Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [RFC PATCH 6/8] tests/qtest/libqtest: Allow checking for HVF accelerator
Date: Thu, 19 Jan 2023 11:05:35 +0100 [thread overview]
Message-ID: <20230119100537.5114-7-philmd@linaro.org> (raw)
In-Reply-To: <20230119100537.5114-1-philmd@linaro.org>
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
---
RFC: CONFIG_HVF is poisoned.
We could pass host config definitions to qtest using:
diff --git a/meson.build b/meson.build
@@ -2547,6 +2547,7 @@ foreach target : target_dirs
accel_kconfig = []
foreach sym: accelerators
+ config_host_data.set(sym + '_QTEST', '')
if sym == 'CONFIG_TCG' or target in accelerator_targets.get(sym, [])
config_target += { sym: 'y' }
config_all += { sym: 'y' }
Then test for CONFIG_HVF_QTEST ...
---
tests/qtest/libqtest.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/qtest/libqtest.c b/tests/qtest/libqtest.c
index 6b2216cb20..31650bdc9f 100644
--- a/tests/qtest/libqtest.c
+++ b/tests/qtest/libqtest.c
@@ -901,6 +901,8 @@ bool qtest_has_accel(const char *accel_name)
}
}
}
+ } else if (g_str_equal(accel_name, "hvf")) {
+ return true; /* XXX CONFIG_HVF is poisoned... */
} else {
/* not implemented */
g_assert_not_reached();
--
2.38.1
next prev parent reply other threads:[~2023-01-19 10:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 10:05 [PATCH 0/8] tests/qtest: Allow running boot-serial / migration with TCG disabled Philippe Mathieu-Daudé
2023-01-19 10:05 ` [PATCH 1/8] tests/qtest/boot-serial-test: Constify tests[] array Philippe Mathieu-Daudé
2023-01-19 10:05 ` [PATCH 2/8] tests/qtest/boot-serial-test: Build command line using GString API Philippe Mathieu-Daudé
2023-01-19 10:05 ` [PATCH 3/8] tests/qtest/boot-serial-test: Only use available accelerators Philippe Mathieu-Daudé
2023-01-19 10:05 ` [PATCH 4/8] tests/qtest/migration-test: Build command line using GString API Philippe Mathieu-Daudé
2023-01-19 10:59 ` Dr. David Alan Gilbert
2023-01-19 11:15 ` Philippe Mathieu-Daudé
2023-01-19 10:05 ` [PATCH 5/8] tests/qtest/migration-test: Only use available accelerators Philippe Mathieu-Daudé
2023-01-19 11:08 ` Dr. David Alan Gilbert
2023-01-19 10:05 ` Philippe Mathieu-Daudé [this message]
2023-01-19 11:24 ` [RFC PATCH 6/8] tests/qtest/libqtest: Allow checking for HVF accelerator Thomas Huth
2023-01-19 11:30 ` Philippe Mathieu-Daudé
2023-01-19 12:05 ` Thomas Huth
2023-01-20 10:26 ` Thomas Huth
2023-01-20 11:18 ` Philippe Mathieu-Daudé
2023-01-20 11:39 ` Thomas Huth
2023-01-19 16:21 ` Thomas Huth
2023-01-19 10:05 ` [PATCH 7/8] tests/qtest/boot-serial-test: Allow running with HVF Philippe Mathieu-Daudé
2023-01-19 10:05 ` [PATCH 8/8] tests/qtest/migration-test: " Philippe Mathieu-Daudé
2023-01-19 11:13 ` Dr. David Alan Gilbert
2023-01-19 11:31 ` 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=20230119100537.5114-7-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=dgilbert@redhat.com \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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).