From: <victorm.lira@amd.com>
To: <xen-devel@lists.xenproject.org>
Cc: Victor Lira <victorm.lira@amd.com>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: [XEN PATCH v1 0/3] automation: add x86_64 test (linux argo)
Date: Thu, 17 Oct 2024 10:18:25 -0700 [thread overview]
Message-ID: <cover.1729183051.git.victorm.lira@amd.com> (raw)
From: Victor Lira <victorm.lira@amd.com>
Add x86_64 hardware test that creates a Xen Argo communication
connection between two PVH domains.
To accomplish this, add new build artifacts for Linux and Argo, and
update the xilinx x86_64 test script.
Victor Lira (3):
automation: add linux 6.6.56 artifact
automation: add linux argo test artifacts
automation: add x86_64 test (linux argo)
automation/gitlab-ci/build.yaml | 34 +++++++
automation/gitlab-ci/test.yaml | 10 ++
.../scripts/xilinx-smoke-dom0-x86_64.sh | 76 ++++++++++-----
.../tests-artifacts/argo/6.6.56.dockerfile | 95 +++++++++++++++++++
.../tests-artifacts/kernel/6.6.56.dockerfile | 54 +++++++++++
5 files changed, 244 insertions(+), 25 deletions(-)
create mode 100644 automation/tests-artifacts/argo/6.6.56.dockerfile
create mode 100644 automation/tests-artifacts/kernel/6.6.56.dockerfile
--
2.25.1
next reply other threads:[~2024-10-17 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 17:18 victorm.lira [this message]
2024-10-17 17:18 ` [XEN PATCH v1 1/3] automation: add linux 6.6.56 artifact victorm.lira
2024-10-17 17:18 ` [XEN PATCH v1 2/3] automation: add linux argo test artifacts victorm.lira
2024-10-17 17:18 ` [XEN PATCH v1 3/3] automation: add x86_64 test (linux argo) victorm.lira
2024-10-17 19:25 ` [XEN PATCH v1 0/3] " Andrew Cooper
2024-10-18 2:44 ` Stefano Stabellini
2024-10-18 11:35 ` Marek Marczykowski-Górecki
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=cover.1729183051.git.victorm.lira@amd.com \
--to=victorm.lira@amd.com \
--cc=cardoe@cardoe.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.