From: Shuah Khan <skhan@linuxfoundation.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Huacai Chen" <chenhuacai@kernel.org>,
"WANG Xuerui" <kernel@xen0n.name>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"David Gow" <davidgow@google.com>, "Rae Moar" <rmoar@google.com>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 2/4] kunit: qemu_configs: add LoongArch config
Date: Thu, 17 Oct 2024 14:27:18 -0600 [thread overview]
Message-ID: <878d5f26-ef05-44f4-93e8-01f66088c0cc@linuxfoundation.org> (raw)
In-Reply-To: <20241014-kunit-loongarch-v1-2-1699b2ad6099@linutronix.de>
Hi Thomas,
On 10/14/24 05:36, Thomas Weißschuh wrote:
> Add a basic config to run kunit tests on LoongArch.
> This requires QEMU 9.1.0 or later for the necessary direct kernel boot
> support.
>
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> ---
> tools/testing/kunit/qemu_configs/loongarch.py | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/tools/testing/kunit/qemu_configs/loongarch.py b/tools/testing/kunit/qemu_configs/loongarch.py
> new file mode 100644
> index 0000000000000000000000000000000000000000..e7bb7c07819677dfdefac012821a732555813cae
> --- /dev/null
> +++ b/tools/testing/kunit/qemu_configs/loongarch.py
Missing SPDX-License-Identifier.
> @@ -0,0 +1,16 @@
> +from ..qemu_config import QemuArchParams
> +
> +QEMU_ARCH = QemuArchParams(linux_arch='loongarch',
> + kconfig='''
> +CONFIG_EFI_STUB=n
> +CONFIG_PCI_HOST_GENERIC=y
> +CONFIG_SERIAL_8250=y
> +CONFIG_SERIAL_8250_CONSOLE=y
> +CONFIG_SERIAL_OF_PLATFORM=y
> +''',
> + qemu_arch='loongarch64',
> + kernel_path='arch/loongarch/boot/vmlinux.elf',
> + kernel_command_line='console=ttyS0',
> + extra_qemu_params=[
> + '-machine', 'virt',
> + '-cpu', 'max',])
>
Please send v2 with all the reviewed by tags. If there
is a resend 3.4 and 4/4 in this series, send them.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-10-17 20:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 11:36 [PATCH 0/4] kunit: Add support for LoongArch Thomas Weißschuh
2024-10-14 11:36 ` [PATCH 1/4] LoongArch: Don't crash in stack_top() for tasks without vDSO Thomas Weißschuh
2024-10-15 2:15 ` Huacai Chen
2024-10-15 6:14 ` Thomas Weißschuh
2024-10-15 6:21 ` Huacai Chen
2024-10-17 7:28 ` David Gow
2024-10-14 11:36 ` [PATCH 2/4] kunit: qemu_configs: add LoongArch config Thomas Weißschuh
2024-10-15 7:31 ` maobibo
2024-10-17 7:24 ` David Gow
2024-10-17 20:27 ` Shuah Khan [this message]
2024-10-17 20:31 ` Thomas Weißschuh
2024-10-17 20:36 ` Shuah Khan
2024-10-14 11:36 ` [PATCH 3/4] kunit: tool: Allow overriding the shutdown mode from qemu config Thomas Weißschuh
2024-10-17 7:24 ` David Gow
2024-10-14 11:36 ` [PATCH 4/4] kunit: qemu_configs: loongarch: Enable shutdown Thomas Weißschuh
2024-10-15 7:31 ` maobibo
2024-10-17 7:25 ` David Gow
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=878d5f26-ef05-44f4-93e8-01f66088c0cc@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=brendan.higgins@linux.dev \
--cc=chenhuacai@kernel.org \
--cc=davidgow@google.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=rmoar@google.com \
--cc=thomas.weissschuh@linutronix.de \
/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