From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-devel@nongnu.org
Cc: Alistair Francis <alistair@alistair23.me>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
qemu-arm@nongnu.org, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH] tests/acceptance: Add a boot test for the xlnx-versal-virt machine
Date: Mon, 25 May 2020 15:13:02 +0200 [thread overview]
Message-ID: <53caef52-ad35-d44b-02a2-e0acd441b9a4@redhat.com> (raw)
In-Reply-To: <20200525072630.22280-1-thuth@redhat.com>
On 5/25/20 9:26 AM, Thomas Huth wrote:
> As described by Edgar here:
>
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg605124.html
>
> we can use the Ubuntu kernel for testing the xlnx-versal-virt machine.
> So let's add a boot test for this now.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/acceptance/boot_linux_console.py | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/tests/acceptance/boot_linux_console.py b/tests/acceptance/boot_linux_console.py
> index 0653c8c1bf..430a6c3b43 100644
> --- a/tests/acceptance/boot_linux_console.py
> +++ b/tests/acceptance/boot_linux_console.py
> @@ -307,6 +307,30 @@ class BootLinuxConsole(Test):
> console_pattern = 'Kernel command line: %s' % kernel_command_line
> self.wait_for_console_pattern(console_pattern)
>
> + def test_aarch64_xlnx_versal_virt(self):
> + """
> + :avocado: tags=arch:aarch64
> + :avocado: tags=machine:xlnx-versal-virt
Thanks for adding this test!
Please also add:
:avocado: tags=device:pl011
:avocado: tags=device:arm_gicv3
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> + """
> + kernel_url = ('http://ports.ubuntu.com/ubuntu-ports/dists/'
> + 'bionic-updates/main/installer-arm64/current/images/'
> + 'netboot/ubuntu-installer/arm64/linux')
> + kernel_hash = '5bfc54cf7ed8157d93f6e5b0241e727b6dc22c50'
> + kernel_path = self.fetch_asset(kernel_url, asset_hash=kernel_hash)
> +
> + initrd_url = ('http://ports.ubuntu.com/ubuntu-ports/dists/'
> + 'bionic-updates/main/installer-arm64/current/images/'
> + 'netboot/ubuntu-installer/arm64/initrd.gz')
> + initrd_hash = 'd385d3e88d53e2004c5d43cbe668b458a094f772'
> + initrd_path = self.fetch_asset(initrd_url, asset_hash=initrd_hash)
> +
> + self.vm.set_console()
> + self.vm.add_args('-m', '2G',
> + '-kernel', kernel_path,
> + '-initrd', initrd_path)
> + self.vm.launch()
> + self.wait_for_console_pattern('Checked W+X mappings: passed')
> +
> def test_arm_virt(self):
> """
> :avocado: tags=arch:arm
>
prev parent reply other threads:[~2020-05-25 13:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 7:26 [PATCH] tests/acceptance: Add a boot test for the xlnx-versal-virt machine Thomas Huth
2020-05-25 13:13 ` 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=53caef52-ad35-d44b-02a2-e0acd441b9a4@redhat.com \
--to=philmd@redhat.com \
--cc=alistair@alistair23.me \
--cc=crosa@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).