From: Thomas Huth <thuth@redhat.com>
To: "Thomas Weißschuh" <thomas@t-8ch.de>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Laurent Vivier" <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
Subject: Re: [PATCH v5 6/6] tests/qtest/pvpanic: add tests for pvshutdown event
Date: Tue, 30 Jan 2024 07:58:35 +0100 [thread overview]
Message-ID: <5e7464a5-209e-457f-b661-e67332cd28b5@redhat.com> (raw)
In-Reply-To: <20240129-pvpanic-shutdown-v5-6-f5a060b87c74@t-8ch.de>
On 29/01/2024 20.28, Thomas Weißschuh wrote:
> Validate that a shutdown via the pvpanic device emits the correct
> QMP events.
>
> Signed-off-by: Thomas Weißschuh <thomas@t-8ch.de>
> ---
> tests/qtest/pvpanic-pci-test.c | 39 +++++++++++++++++++++++++++++++++++++++
> tests/qtest/pvpanic-test.c | 29 +++++++++++++++++++++++++++++
> 2 files changed, 68 insertions(+)
>
> diff --git a/tests/qtest/pvpanic-pci-test.c b/tests/qtest/pvpanic-pci-test.c
> index b372caf41dc0..e1c05d383219 100644
> --- a/tests/qtest/pvpanic-pci-test.c
> +++ b/tests/qtest/pvpanic-pci-test.c
> @@ -85,11 +85,50 @@ static void test_panic(void)
> qtest_quit(qts);
> }
>
> +static void test_pvshutdown(void)
> +{
> + uint8_t val;
> + QDict *response, *data;
> + QTestState *qts;
> + QPCIBus *pcibus;
> + QPCIDevice *dev;
> + QPCIBar bar;
> +
> + qts = qtest_init("-device pvpanic-pci,addr=04.0");
> + pcibus = qpci_new_pc(qts, NULL);
> + dev = qpci_device_find(pcibus, QPCI_DEVFN(0x4, 0x0));
> + qpci_device_enable(dev);
> + bar = qpci_iomap(dev, 0, NULL);
> +
> + qpci_memread(dev, bar, 0, &val, sizeof(val));
> + g_assert_cmpuint(val, ==, PVPANIC_EVENTS);
> +
> + val = 4;
Could you use PVPANIC_SHUTDOWN here instead of the magic value?
> + qpci_memwrite(dev, bar, 0, &val, sizeof(val));
> +
> + response = qtest_qmp_eventwait_ref(qts, "GUEST_PVSHUTDOWN");
> + qobject_unref(response);
> +
> + response = qtest_qmp_eventwait_ref(qts, "SHUTDOWN");
> + g_assert(qdict_haskey(response, "data"));
> + data = qdict_get_qdict(response, "data");
> + g_assert(qdict_haskey(data, "guest"));
> + g_assert(qdict_get_bool(data, "guest"));
> + g_assert(qdict_haskey(data, "reason"));
> + g_assert_cmpstr(qdict_get_str(data, "reason"), ==, "guest-shutdown");
> + qobject_unref(response);
> +
> + g_free(dev);
> + qpci_free_pc(pcibus);
> + qtest_quit(qts);
> +}
> +
> int main(int argc, char **argv)
> {
> g_test_init(&argc, &argv, NULL);
> qtest_add_func("/pvpanic-pci/panic", test_panic);
> qtest_add_func("/pvpanic-pci/panic-nopause", test_panic_nopause);
> + qtest_add_func("/pvpanic-pci/pvshutdown", test_pvshutdown);
>
> return g_test_run();
> }
> diff --git a/tests/qtest/pvpanic-test.c b/tests/qtest/pvpanic-test.c
> index ccc603472f5d..ff1f25f46586 100644
> --- a/tests/qtest/pvpanic-test.c
> +++ b/tests/qtest/pvpanic-test.c
> @@ -58,11 +58,40 @@ static void test_panic(void)
> qtest_quit(qts);
> }
>
> +static void test_pvshutdown(void)
> +{
> + uint8_t val;
> + QDict *response, *data;
> + QTestState *qts;
> +
> + qts = qtest_init("-device pvpanic");
> +
> + val = qtest_inb(qts, 0x505);
> + g_assert_cmpuint(val, ==, PVPANIC_EVENTS);
> +
> + qtest_outb(qts, 0x505, 0x4);
dito, use PVPANIC_SHUTDOWN instead of 4 ?
(as a separate clean-up, we should maybe also introduce a #define for 0x505
one day, but that's something for another patch)
> + response = qtest_qmp_eventwait_ref(qts, "GUEST_PVSHUTDOWN");
> + qobject_unref(response);
> +
> + response = qtest_qmp_eventwait_ref(qts, "SHUTDOWN");
> + g_assert(qdict_haskey(response, "data"));
> + data = qdict_get_qdict(response, "data");
> + g_assert(qdict_haskey(data, "guest"));
> + g_assert(qdict_get_bool(data, "guest"));
> + g_assert(qdict_haskey(data, "reason"));
> + g_assert_cmpstr(qdict_get_str(data, "reason"), ==, "guest-shutdown");
> + qobject_unref(response);
> +
> + qtest_quit(qts);
> +}
> +
> int main(int argc, char **argv)
> {
> g_test_init(&argc, &argv, NULL);
> qtest_add_func("/pvpanic/panic", test_panic);
> qtest_add_func("/pvpanic/panic-nopause", test_panic_nopause);
> + qtest_add_func("/pvpanic/pvshutdown", test_pvshutdown);
>
> return g_test_run();
> }
>
With PVPANIC_SHUTDOWN instead of 4:
Reviewed-by: Thomas Huth <thuth@redhat.com>
prev parent reply other threads:[~2024-01-30 6:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 19:28 [PATCH v5 0/6] hw/misc/pvpanic: add support for normal shutdowns Thomas Weißschuh
2024-01-29 19:28 ` [PATCH v5 1/6] linux-headers: drop pvpanic.h Thomas Weißschuh
2024-01-29 19:28 ` [PATCH v5 2/6] hw/misc/pvpanic: centralize definition of supported events Thomas Weißschuh
2024-01-29 19:28 ` [PATCH v5 3/6] tests/qtest/pvpanic: use centralized " Thomas Weißschuh
2024-01-29 19:28 ` [PATCH v5 4/6] hw/misc/pvpanic: add support for normal shutdowns Thomas Weißschuh
2024-01-29 19:28 ` [PATCH v5 5/6] pvpanic: Emit GUEST_PVSHUTDOWN QMP event on pvpanic shutdown signal Thomas Weißschuh
2024-01-29 19:28 ` [PATCH v5 6/6] tests/qtest/pvpanic: add tests for pvshutdown event Thomas Weißschuh
2024-01-30 6:58 ` Thomas Huth [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=5e7464a5-209e-457f-b661-e67332cd28b5@redhat.com \
--to=thuth@redhat.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=cohuck@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas@t-8ch.de \
/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).