From: David Woodhouse <dwmw2@infradead.org>
To: "Remi Duraffort" <remi.duraffort@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Vikram Garhwal <vikram.garhwal@amd.com>,
Stefano Stabellini <stefano.stabellini@amd.com>
Subject: Re: Adding default config options to the tuxrun baseline kernels and enabling sshd
Date: Fri, 24 Mar 2023 13:26:40 +0000 [thread overview]
Message-ID: <3e6fb10defaac2ac0e6445e61631b6b612672ddd.camel@infradead.org> (raw)
In-Reply-To: <CANJfhHe-E-+F_P_=+ww46Szp_To=C4QWxKG5hdeCriwQr821jg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1589 bytes --]
On Fri, 2023-03-24 at 13:53 +0100, Remi Duraffort wrote:
> Le ven. 24 mars 2023 à 12:02, Alex Bennée <alex.bennee@linaro.org> a écrit :
> > version: 1
> > name: Xen Guest Kernels
> > description: Build Xen Test Kernels
> > jobs:
> > - builds:
> > - {target_arch: x86_64, toolchain: gcc-12, kconfig: [defconfig, "CONFIG_XEN=y", "CONFIG_XEN_PVHVM=y", "CONFIG_XEN_BLKDEV_FRONTEND=y", "CONFIG_XEN_PVHVM_GUEST=y"]}
> > - {target_arch: i386, toolchain: gcc-12, kconfig: [defconfig, "CONFIG_XEN=y", "CONFIG_XEN_PVHVM=y", "CONFIG_XEN_BLKDEV_FRONTEND=y", "CONFIG_XEN_PVHVM_GUEST=y"]}
> > test: {device: qemu-x86_64, tests: [ltp-smoke]}
>
>
> The kernels and rootfs are built by this gitlab
> project: https://gitlab.com/LinaroLtd/tuxsuite.com/tuxtest/tuxtest-bu
> ildroot using buildroot.
> So for sure we can add sshd support quickly. Regarding the support
> for xen, this can be added for arm64 if you want (only arm64 or
> something else)?
Thanks. This request was for x86_64 and i386 kernels, rather than
arm64.
I think arm64 Xen support is coming to qemu but it requires real Xen —
while what we're wanting to test here is *emulating* Xen on Linux/KVM,
which isn't something that we support on arm64. So I suspect there's
not a lot of benefit in adding it to the arm64 builds? Vikram, Stefano,
what do you think?
Adding CONFIG_XEN_NETDEV_FRONTEND=y in addition to the above options
would be appreciated too please; we haven't yet made that actually work
in the Xen emulation but we plan to fairly soon.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2023-03-24 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 10:47 Adding default config options to the tuxrun baseline kernels and enabling sshd Alex Bennée
2023-03-24 12:53 ` Remi Duraffort
2023-03-24 13:26 ` David Woodhouse [this message]
2023-03-24 19:48 ` Stefano Stabellini
2023-03-24 17:11 ` 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=3e6fb10defaac2ac0e6445e61631b6b612672ddd.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.bennee@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=remi.duraffort@linaro.org \
--cc=stefano.stabellini@amd.com \
--cc=vikram.garhwal@amd.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).