From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: xen-devel@lists.xenproject.org
Cc: Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Gianluca Guida <gianluca@rivosinc.com>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>,
Bob Eshleman <bobbyeshleman@gmail.com>,
Alistair Francis <alistair.francis@wdc.com>,
Connor Davis <connojdavis@gmail.com>,
Doug Goldstein <cardoe@cardoe.com>
Subject: [PATCH v9 0/2] Basic early_printk and smoke test implementation
Date: Tue, 7 Feb 2023 14:41:51 +0200 [thread overview]
Message-ID: <cover.1675772422.git.oleksii.kurochko@gmail.com> (raw)
The patch series introduces the following:
- the minimal set of headers and changes inside them.
- SBI (RISC-V Supervisor Binary Interface) things necessary for basic
early_printk implementation.
- things needed to set up the stack.
- early_printk() function to print only strings.
- RISC-V smoke test which checks if "Hello from C env" message is
present in serial.tmp
The patch series is rebased on top of the patch "include/types: move
stddef.h-kind types to common header" [1]
[1] https://lore.kernel.org/xen-devel/5a0a9e2a-c116-21b5-8081-db75fe4178d7@suse.com/
---
Changes in V9:
- Bring "cmodel=medany" check back to be sure that C function is safe to be called
in early boot when MMU is off as
---
Changes in V8:
- Set "needs: archlinux-current-gcc-riscv64-debug" in test.yaml
for RISCV job as CONFIG_EARLY_PRINTK is available only when
CONFIG_DEBUG is available.
---
Changes in V7:
- Fix dependecy for qemu-smoke-riscv64-gcc job
---
Changes in V6:
- Rename container name in test.yaml for .qemu-riscv64.
---
Changes in V5:
- Nothing changed
---
Changes in V4:
- Nothing changed
---
Changes in V3:
- Nothing changed
- All mentioned comments by Stefano in Xen mailing list will be
fixed as a separate patch out of this patch series.
---
Oleksii Kurochko (2):
xen/riscv: introduce early_printk basic stuff
automation: add RISC-V smoke test
automation/gitlab-ci/test.yaml | 20 ++++++++++++++
automation/scripts/qemu-smoke-riscv64.sh | 20 ++++++++++++++
xen/arch/riscv/Kconfig.debug | 5 ++++
xen/arch/riscv/Makefile | 1 +
xen/arch/riscv/early_printk.c | 33 +++++++++++++++++++++++
xen/arch/riscv/include/asm/early_printk.h | 12 +++++++++
xen/arch/riscv/setup.c | 4 +++
7 files changed, 95 insertions(+)
create mode 100755 automation/scripts/qemu-smoke-riscv64.sh
create mode 100644 xen/arch/riscv/early_printk.c
create mode 100644 xen/arch/riscv/include/asm/early_printk.h
--
2.39.0
next reply other threads:[~2023-02-07 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 12:41 Oleksii Kurochko [this message]
2023-02-07 12:41 ` [PATCH v9 1/2] xen/riscv: introduce early_printk basic stuff Oleksii Kurochko
2023-02-07 12:41 ` [PATCH v9 2/2] automation: add RISC-V smoke test Oleksii Kurochko
2023-02-07 12:49 ` [PATCH v9 0/2] Basic early_printk and smoke test implementation Oleksii
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.1675772422.git.oleksii.kurochko@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=bobbyeshleman@gmail.com \
--cc=cardoe@cardoe.com \
--cc=connojdavis@gmail.com \
--cc=gianluca@rivosinc.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--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 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).