From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Nicholas Piggin <npiggin@gmail.com>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>,
"Alexey Kardashevskiy" <aik@ozlabs.ru>
Subject: Re: [PATCH] tests/avocado: ppc test VOF bios Linux boot
Date: Fri, 23 Jun 2023 17:37:25 +0200 [thread overview]
Message-ID: <ca2121fd-e430-f3f7-48fa-5ff3bb6ffe7b@linaro.org> (raw)
In-Reply-To: <20230623122135.320261-1-npiggin@gmail.com>
On 23/6/23 14:21, Nicholas Piggin wrote:
> VOF is the new lightweight fast pseries bios. Add a Linux boot test
> using VOF.
>
> More tests could be moved to use VOF becasue it's much faster, but
Typo "because".
> just dip one toe in the water first here. SLOF should continue to be
> tested too.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---
>
> This applies on top of the SMP/SMT avocado test I sent. Just
> thought it would be a nice addition.
>
> Thanks,
> Nick
>
> tests/avocado/ppc_pseries.py | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/tests/avocado/ppc_pseries.py b/tests/avocado/ppc_pseries.py
> index ff42c770f2..a8311e6555 100644
> --- a/tests/avocado/ppc_pseries.py
> +++ b/tests/avocado/ppc_pseries.py
> @@ -29,6 +29,17 @@ def do_test_ppc64_linux_boot(self):
> '-append', kernel_command_line)
> self.vm.launch()
>
> + def test_ppc64_vof_linux_boot(self):
> + """
> + :avocado: tags=arch:ppc64
> + :avocado: tags=machine:pseries
Note, you could add 'tags:firmware:vof' if filtering to run only tests
booting VOF is useful.
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2023-06-23 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 12:21 [PATCH] tests/avocado: ppc test VOF bios Linux boot Nicholas Piggin
2023-06-23 15:37 ` 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=ca2121fd-e430-f3f7-48fa-5ff3bb6ffe7b@linaro.org \
--to=philmd@linaro.org \
--cc=aik@ozlabs.ru \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--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).