From: Fabiano Rosas <farosas@suse.de>
To: "Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] tests/qtest/q35-test: Remove the obsolete test_without_smram_base test
Date: Thu, 08 May 2025 10:41:43 -0300 [thread overview]
Message-ID: <87h61vfcdk.fsf@suse.de> (raw)
In-Reply-To: <20250508095122.144807-1-thuth@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> From: Thomas Huth <thuth@redhat.com>
>
> With the release of QEMU 10.1, the pc-q35-4.1 machine will be older
> than 6 years and thus will get disabled automatically by the
> MACHINE_VER_DELETION() macro. Remove the related test to avoid
> that the q35-test is failing when the machine is not available anymore.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/qtest/q35-test.c | 37 +------------------------------------
> 1 file changed, 1 insertion(+), 36 deletions(-)
>
> diff --git a/tests/qtest/q35-test.c b/tests/qtest/q35-test.c
> index 75d4078b790..62fff49fc89 100644
> --- a/tests/qtest/q35-test.c
> +++ b/tests/qtest/q35-test.c
> @@ -246,41 +246,6 @@ static void test_smram_smbase_lock(void)
> qtest_quit(qts);
> }
>
> -static void test_without_smram_base(void)
> -{
> - QPCIBus *pcibus;
> - QPCIDevice *pcidev;
> - QTestState *qts;
> - int i;
> -
> - qts = qtest_init("-M pc-q35-4.1");
> -
> - pcibus = qpci_new_pc(qts, NULL);
> - g_assert(pcibus != NULL);
> -
> - pcidev = qpci_device_find(pcibus, 0);
> - g_assert(pcidev != NULL);
> -
> - /* check that RAM is accessible */
> - qtest_writeb(qts, SMBASE, SMRAM_TEST_PATTERN);
> - g_assert_cmpint(qtest_readb(qts, SMBASE), ==, SMRAM_TEST_PATTERN);
> -
> - /* check that writing to 0x9c succeeds */
> - for (i = 0; i <= 0xff; i++) {
> - qpci_config_writeb(pcidev, MCH_HOST_BRIDGE_F_SMBASE, i);
> - g_assert(qpci_config_readb(pcidev, MCH_HOST_BRIDGE_F_SMBASE) == i);
> - }
> -
> - /* check that RAM is still accessible */
> - qtest_writeb(qts, SMBASE, SMRAM_TEST_PATTERN + 1);
> - g_assert_cmpint(qtest_readb(qts, SMBASE), ==, (SMRAM_TEST_PATTERN + 1));
> -
> - g_free(pcidev);
> - qpci_free_pc(pcibus);
> -
> - qtest_quit(qts);
> -}
> -
> int main(int argc, char **argv)
> {
> g_test_init(&argc, &argv, NULL);
> @@ -293,6 +258,6 @@ int main(int argc, char **argv)
> qtest_add_data_func("/q35/tseg-size/ext/16mb", &tseg_ext_16mb,
> test_tseg_size);
> qtest_add_func("/q35/smram/smbase_lock", test_smram_smbase_lock);
> - qtest_add_func("/q35/smram/legacy_smbase", test_without_smram_base);
> +
> return g_test_run();
> }
Queued, thanks!
next prev parent reply other threads:[~2025-05-08 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 9:51 [PATCH] tests/qtest/q35-test: Remove the obsolete test_without_smram_base test Thomas Huth
2025-05-08 9:57 ` Daniel P. Berrangé
2025-05-08 11:17 ` Philippe Mathieu-Daudé
2025-05-08 13:41 ` Fabiano Rosas [this message]
2025-05-08 16:17 ` Daniel P. Berrangé
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=87h61vfcdk.fsf@suse.de \
--to=farosas@suse.de \
--cc=berrange@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--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).