From: Cleber Rosa <crosa@redhat.com>
To: Wainer dos Santos Moschetta <wainersm@redhat.com>
Cc: fam@euphon.net, alex.bennee@linaro.org, qemu-devel@nongnu.org,
wrampazz@redhat.com, philmd@redhat.com, sgarzare@redhat.com
Subject: Re: [PATCH 1/2] tests/acceptance: Add PVH boot test
Date: Fri, 6 Dec 2019 11:54:19 -0500 [thread overview]
Message-ID: <20191206165419.GC23522@dhcp-17-72.bos.redhat.com> (raw)
In-Reply-To: <20191206140012.15517-2-wainersm@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4201 bytes --]
On Fri, Dec 06, 2019 at 09:00:11AM -0500, Wainer dos Santos Moschetta wrote:
> QEMU 4.0 onward is able to boot an uncompressed kernel
> image by using the x86/HVM direct boot ABI. It needs
> Linux >= 4.21 built with CONFIG_PVH=y.
>
> This introduces an acceptance test which checks an
> uncompressed Linux kernel image boots properly.
>
> Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
> ---
> tests/acceptance/pvh.py | 48 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 48 insertions(+)
> create mode 100644 tests/acceptance/pvh.py
>
> diff --git a/tests/acceptance/pvh.py b/tests/acceptance/pvh.py
> new file mode 100644
> index 0000000000..c68489c273
> --- /dev/null
> +++ b/tests/acceptance/pvh.py
> @@ -0,0 +1,48 @@
> +# Copyright (c) 2019 Red Hat, Inc.
> +#
> +# Author:
> +# Wainer dos Santos Moschetta <wainersm@redhat.com>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2 or
> +# later. See the COPYING file in the top-level directory.
> +
> +"""
> +x86/HVM direct boot acceptance tests.
> +"""
> +
> +from avocado.utils.kernel import KernelBuild
> +from avocado_qemu import Test
> +from avocado_qemu import wait_for_console_pattern
> +
> +
> +class Pvh(Test):
> + """
> + Test suite for x86/HVM direct boot feature.
> +
> + :avocado: tags=slow,arch=x86_64,machine=q35
> + """
> + def test_boot_vmlinux(self):
> + """
> + Boot uncompressed kernel image.
> + """
> + # QEMU can boot a vmlinux image for kernel >= 4.21 built
> + # with CONFIG_PVH=y
> + kernel_version = '5.4.1'
> + kbuild = KernelBuild(kernel_version, work_dir=self.workdir)
> + try:
> + kbuild.download()
> + kbuild.uncompress()
> + kbuild.configure(targets=['defconfig', 'kvmconfig'],
> + extra_configs=['CONFIG_PVH=y'])
I'm aware of the reason why this uses APIs not fulfilled by
tests/requirements.txt, but, for the general public reviewing/testing
code with extra requirements, it's a good idea to bump the
requirements to a version that fulfills the requirement, and comment
out clearly on the temporary nature of the change (marking the patch).
For instance, for this requirement, we could have:
diff --git a/tests/requirements.txt b/tests/requirements.txt
index a2a587223a..5498d67bc1 100644
--- a/tests/requirements.txt
+++ b/tests/requirements.txt
@@ -1,4 +1,5 @@
# Add Python module requirements, one per line, to be installed
# in the tests/venv Python virtual environment. For more info,
# refer to: https://pip.pypa.io/en/stable/user_guide/#id1
-avocado-framework==72.0
+# [REMOVE ME] use post 73.0 Avocado containing the new kernel build APIs
+-e git+https://github.com/avocado-framework/avocado@d6fb24edcf847f09c312b55df3c674c64c79793e#egg=avocado_framework
This will not only help people to test it, but should also make
it work transparently on CI.
> + kbuild.build()
As stated in my response to the cover letter, I think we need to move
this elsewhere. The *very* minimum is to have this in a setUp()
method, but we should strongly consider other solutions.
> + except:
> + self.cancel("Unable to build vanilla kernel %s" % kernel_version)
> +
> + self.vm.set_machine('q35')
> + self.vm.set_console()
> + kernel_command_line = 'printk.time=0 console=ttyS0'
> + self.vm.add_args('-kernel', kbuild.vmlinux,
> + '-append', kernel_command_line)
And just for being thorough (and purist? idealistic? Utopian? :), if
we stop and think about it, the following two lines are really what
this test is all about. Everything else should be the test's setup.
I'm not arguing in favor of being radical and reject anything that is
not perfect, but just reminding ourselves (myself very much included)
of this general direction.
Cheers,
- Cleber.
> + self.vm.launch()
> + wait_for_console_pattern(self, 'Kernel command line: %s' %
> + kernel_command_line)
> --
> 2.21.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-06 17:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 14:00 [PATCH 0/2] tests/acceptance: Add boot vmlinux test Wainer dos Santos Moschetta
2019-12-06 14:00 ` [PATCH 1/2] tests/acceptance: Add PVH boot test Wainer dos Santos Moschetta
2019-12-06 15:04 ` Willian Rampazzo
2019-12-06 16:54 ` Cleber Rosa [this message]
2019-12-09 14:43 ` Wainer dos Santos Moschetta
2019-12-10 2:21 ` Cleber Rosa
2019-12-10 11:16 ` Philippe Mathieu-Daudé
2019-12-06 14:00 ` [PATCH 2/2] .travis.yml: Add kernel build deps for acceptance tests Wainer dos Santos Moschetta
2019-12-12 12:22 ` Alex Bennée
2019-12-06 16:42 ` [PATCH 0/2] tests/acceptance: Add boot vmlinux test Cleber Rosa
2019-12-10 11:05 ` Alex Bennée
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=20191206165419.GC23522@dhcp-17-72.bos.redhat.com \
--to=crosa@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=fam@euphon.net \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).