From: David Woodhouse <dwmw2@infradead.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Paul Durrant" <paul@xen.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 3/3] tests/avocado: Test Xen guest support under KVM
Date: Wed, 08 Mar 2023 19:07:40 +0000 [thread overview]
Message-ID: <03830c7daa0ac4388c5b2811889e63b200340773.camel@infradead.org> (raw)
In-Reply-To: <87lek7nncp.fsf@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2331 bytes --]
On Wed, 2023-03-08 at 17:45 +0000, Alex Bennée wrote:
>
> David Woodhouse <dwmw2@infradead.org> writes:
>
> > From: David Woodhouse <dwmw@amazon.co.uk>
> >
> > Exercise guests with a few different modes for interrupt delivery. In
> > particular we want to cover:
> >
> > • Xen event channel delivery via GSI to the I/O APIC
> > • Xen event channel delivery via GSI to the i8259 PIC
> > • MSIs routed to PIRQ event channels
> > • GSIs routed to PIRQ event channels
> >
> > As well as some variants of normal non-Xen stuff like MSI to vAPIC and
> > PCI INTx going to the I/O APIC and PIC, which ought to still work even
> > in Xen mode.
> >
> > Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> > ---
> > tests/avocado/xen_guest.py | 147 +++++++++++++++++++++++++++++++++++++
> > 1 file changed, 147 insertions(+)
> > create mode 100644 tests/avocado/xen_guest.py
> >
> > diff --git a/tests/avocado/xen_guest.py b/tests/avocado/xen_guest.py
> > new file mode 100644
> > index 0000000000..c50b52958f
> > --- /dev/null
> > +++ b/tests/avocado/xen_guest.py
> > @@ -0,0 +1,147 @@
> > +# Xen guest functional tests
> > +#
>
> Perhaps to avoid confusion we should call the file kvm_xen_guests.py and
> make it clearer in the comment this is the mode we are talking about.
> c.f. the boot_xen.py tests which boot Xen (under TCG emulation) as a
> proper hypervisor.
Ack. I'll change it.
> > +# Copyright © 2021 Red Hat, Inc.
> > +# Copyright © 2023 Amazon.com, Inc. or its affiliates. All Rights Reserved.
> > +#
> > +# Author:
> > +# David Woodhouse <dwmw2@infradead.org>
> > +#
> > +# This work is licensed under the terms of the GNU GPL, version 2 or
> > +# later. See the COPYING file in the top-level directory.
> > +import os
> > +
> > +from avocado import skipIf
> > +from avocado_qemu import LinuxTest
> > +
> > +@skipIf(os.getenv('GITLAB_CI'), 'Running on GitLab')
>
> This just means we will never have CI coverage. In theory when running
> on the GitLab shared runners the test should skip anyway when it can't
> find /dev/kvm and hopefully can run on our custom runners when it can
> see /dev/kvm.
>
That one was just cargo-culted from the Intel IOMMU test which I
started from. Happy to drop that if it's redundant.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
prev parent reply other threads:[~2023-03-08 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 11:19 [PATCH v2 0/3] Enable avocado testing for Xen guests David Woodhouse
2023-03-08 11:19 ` [PATCH v2 1/3] hw/intc/ioapic: Update KVM routes before redelivering IRQ, on RTE update David Woodhouse
2023-03-09 11:44 ` Paolo Bonzini
2023-03-08 11:19 ` [PATCH v2 2/3] tests/avocado: Add Fedora 34 distro, including kernel/initrd checksums David Woodhouse
2023-03-08 17:42 ` Alex Bennée
2023-03-08 19:20 ` David Woodhouse
2023-03-09 8:51 ` David Woodhouse
2023-03-08 11:19 ` [PATCH v2 3/3] tests/avocado: Test Xen guest support under KVM David Woodhouse
2023-03-08 17:45 ` Alex Bennée
2023-03-08 19:07 ` David Woodhouse [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=03830c7daa0ac4388c5b2811889e63b200340773.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).