From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Eric Auger <eric.auger@redhat.com>,
eric.auger.pro@gmail.com, qemu-devel@nongnu.org,
crosa@redhat.com, wainersm@redhat.com
Cc: wrampazz@redhat.com, peterx@redhat.com
Subject: Re: [PATCH v5 3/4] avocado_qemu: Add SMMUv3 tests
Date: Tue, 6 Jul 2021 15:34:53 +0200 [thread overview]
Message-ID: <cc5d8c32-4014-96aa-73cd-da0c4d41a59a@redhat.com> (raw)
In-Reply-To: <20210706131729.30749-4-eric.auger@redhat.com>
On 7/6/21 3:17 PM, Eric Auger wrote:
> Add new tests checking the good behavior of the SMMUv3 protecting
> 2 virtio pci devices (block and net). We check the guest boots and
> we are able to install a package. Different guest configs are tested:
> standard, passthrough an strict=0. This is tested with both fedora 31 and
> 33. The former uses a 5.3 kernel without range invalidation whereas the
> latter uses a 5.8 kernel that features range invalidation.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
> Reviewed-by: Willian Rampazzo <willianr@redhat.com>
> Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
> Tested-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
>
> ---
>
> v4 -> v5:
> - Added the skipIf statement (William) and William's R-b
> - added Wainer's R-b and T-b
> ---
> tests/acceptance/smmu.py | 133 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 133 insertions(+)
> create mode 100644 tests/acceptance/smmu.py
> + def run_and_check(self):
> + if self.kernel_path:
> + self.vm.add_args('-kernel', self.kernel_path,
> + '-append', self.kernel_params,
> + '-initrd', self.initrd_path)
> + self.launch_and_wait()
IIUC above is the 'run' part and below is the 'check' part?
So the check succeed if the VM booted, right?
> + self.ssh_command('cat /proc/cmdline')
> + self.ssh_command('dnf -y install numactl-devel')
> +
> +
> + # 5.3 kernel without RIL #
> +
> + def test_smmu_noril(self):
> + """
> + :avocado: tags=smmu_noril
> + :avocado: tags=smmu_noril_tests
> + :avocado: tags=distro_version:31
> + """
> + self.common_vm_setup()
> + self.run_and_check()
next prev parent reply other threads:[~2021-07-06 13:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 13:17 [PATCH v5 0/4] avocado-qemu: New SMMUv3 and intel IOMMU tests Eric Auger
2021-07-06 13:17 ` [PATCH v5 1/4] avocado_qemu: Fix KNOWN_DISTROS map into the LinuxDistro class Eric Auger
2021-07-08 1:17 ` Cleber Rosa
2021-07-08 8:56 ` Eric Auger
2021-07-08 17:34 ` Cleber Rosa
2021-07-08 19:32 ` Eric Auger
2021-07-12 13:26 ` Cleber Rosa
2021-07-09 19:41 ` Wainer dos Santos Moschetta
2021-07-06 13:17 ` [PATCH v5 2/4] Acceptance Tests: Add default kernel params and pxeboot url to the KNOWN_DISTROS collection Eric Auger
2021-07-08 1:25 ` Cleber Rosa
2021-07-06 13:17 ` [PATCH v5 3/4] avocado_qemu: Add SMMUv3 tests Eric Auger
2021-07-06 13:34 ` Philippe Mathieu-Daudé [this message]
2021-07-06 13:57 ` Eric Auger
2021-07-06 14:25 ` Philippe Mathieu-Daudé
2021-07-06 14:39 ` Willian Rampazzo
2021-07-06 14:55 ` Philippe Mathieu-Daudé
2021-07-06 13:17 ` [PATCH v5 4/4] avocado_qemu: Add Intel iommu tests Eric Auger
2021-07-09 20:44 ` Wainer dos Santos Moschetta
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=cc5d8c32-4014-96aa-73cd-da0c4d41a59a@redhat.com \
--to=philmd@redhat.com \
--cc=crosa@redhat.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).