qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Jason Wang" <jasowang@redhat.com>
Cc: eric.auger@redhat.com, qemu-devel@nongnu.org,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Cédric Le Goater" <clg@kaod.org>,
	"Clément Mathieu--Drif" <clement.mathieu--drif@eviden.com>,
	"Yi Liu" <yi.l.liu@intel.com>
Subject: Re: [PATCH for-10.0] tests/functional: Convert the intel_iommu avocado test
Date: Mon, 9 Dec 2024 17:31:37 +0100	[thread overview]
Message-ID: <4fa944df-ddf2-48be-bbb0-7b24f63263e6@linaro.org> (raw)
In-Reply-To: <Z1az26HxcIHVlB-d@redhat.com>

On 9/12/24 10:09, Daniel P. Berrangé wrote:
> On Mon, Dec 09, 2024 at 09:26:21AM +0100, Thomas Huth wrote:
>> On 09/12/2024 09.12, Eric Auger wrote:
>>> Hi Thomas,
>>>
>>> On 12/6/24 19:17, Thomas Huth wrote:
>>>> Convert the intel_iommu test to the new functional framework.
>>>> This test needs some changes since we neither support the old 'LinuxTest'
>>>> class in the functional framework yet, nor a way to use SSH for running
>>>> commands in the guest. So we now directly download a Fedora kernel and
>>>> initrd and set up the serial console for executing the commands and for
>>>> looking for the results.
>>>>
>>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>>> ---
>>>>    MAINTAINERS                                   |   1 +
>>>>    tests/functional/meson.build                  |   1 +
>>>>    .../test_intel_iommu.py}                      | 119 ++++++++----------
>>>>    3 files changed, 51 insertions(+), 70 deletions(-)
>>>>    rename tests/{avocado/intel_iommu.py => functional/test_intel_iommu.py} (41%)
>>>>    mode change 100644 => 100755


>>>> -        self.launch_and_wait()
>>>> -        self.ssh_command('cat /proc/cmdline')
>>>> -        self.ssh_command('dmesg | grep -e DMAR -e IOMMU')
>>>> -        self.ssh_command('find /sys/kernel/iommu_groups/ -type l')
>>>> -        self.ssh_command('dnf -y install numactl-devel')
>>> I understand you cannot use ssh yet but the bulk of the test was the
>>> execution of the dnf install meaning we lose the main substance of it
>>> through the conversion.
>>
>> Ah, I see, so this was exercising the virtio-net device with the IOMMU ...
>> and I already wondered why there was this "dnf install" at the end without
>> doing anything with  the numactl-devel package ... (a comment would have
>> been helpful here)
> 
> FYI, I find 'dnf instal' to be a *highly* undesirable thing todo in
> our test functional. Its performance is highly non-deterministic
> depending on what mirror you happen to get sent to, such that it could
> easily push us over the timeouts. It is also susceptible to periodic
> broken mirrors, and instability around time of Fefdora EOL. I can't
> remember if it was this test case, or a different one, but I've seen
> problems before in avocado with 'dnf install'.
> 
> If we want to test working networking, then can we arrange for something
> more simple & targetted to run, with better worst case performance.

Could we use 2 virtio-net interfaces inter-connected and stress with
https://linux.die.net/man/1/ab ?


  parent reply	other threads:[~2024-12-09 16:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 18:17 [PATCH for-10.0] tests/functional: Convert the intel_iommu avocado test Thomas Huth
2024-12-09  6:39 ` CLEMENT MATHIEU--DRIF
2024-12-09  6:45 ` Cédric Le Goater
2024-12-09  8:12 ` Eric Auger
2024-12-09  8:26   ` Thomas Huth
2024-12-09  8:58     ` Eric Auger
2024-12-09  9:09     ` Daniel P. Berrangé
2024-12-09  9:25       ` Thomas Huth
2024-12-09 10:24         ` Eric Auger
2024-12-09 16:31       ` Philippe Mathieu-Daudé [this message]
2024-12-09 16:37         ` Daniel P. Berrangé
2024-12-09 17:26           ` Thomas Huth

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=4fa944df-ddf2-48be-bbb0-7b24f63263e6@linaro.org \
    --to=philmd@linaro.org \
    --cc=berrange@redhat.com \
    --cc=clement.mathieu--drif@eviden.com \
    --cc=clg@kaod.org \
    --cc=eric.auger@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=yi.l.liu@intel.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).