From: Julien Grall <julien@xen.org>
To: Oleksii <oleksii.kurochko@gmail.com>, xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Gianluca Guida <gianluca@rivosinc.com>,
Bob Eshleman <bobbyeshleman@gmail.com>,
Alistair Francis <alistair.francis@wdc.com>,
Connor Davis <connojdavis@gmail.com>
Subject: Re: [PATCH v1 4/8] xen/riscv: introduce sbi call to putchar to console
Date: Mon, 9 Jan 2023 11:11:04 +0000 [thread overview]
Message-ID: <5531505f-b04b-7b70-68da-18d804790c25@xen.org> (raw)
In-Reply-To: <0475c058d0655f5b7b245f19b20c5ef0f14b3618.camel@gmail.com>
Hi Oleksii,
On 09/01/2023 09:04, Oleksii wrote:
> On Fri, 2023-01-06 at 13:40 +0000, Julien Grall wrote:
>> Hi,
>>
>> On 06/01/2023 13:14, Oleksii Kurochko wrote:
>>> The patch introduce sbi_putchar() SBI call which is necessary
>>> to implement initial early_printk
>>>
>>> Signed-off-by: Oleksii Kurochko <oleksii.kurochko@gmail.com>
>>> ---
>>> xen/arch/riscv/Makefile | 1 +
>>> xen/arch/riscv/include/asm/sbi.h | 34 ++++++++++++++++++++++++
>>> xen/arch/riscv/sbi.c | 44
>>> ++++++++++++++++++++++++++++++++
>>
>> IMHO, it would be better to implement sbi.c in assembly so you can
>> use
>> print in the console before you jump to C world.
>>
> I thought that we can live with C version as we set up stack from the
> start and then we can call early_printk() from assembly code too.
> Is it bad approach?
It depends on how early you want to call it. For Arm, we chose to use
assembly because the C code may not be PIE (and even with PIE it may
need some relocation work).
Andrew suggested that this may not be a problem with RISC-V. I have
looked a bit more around and notice that the kernel is also calling some
C function very early (like setup_vm()). But they ensure that the code
is built with -mcmodel=medany.
It looks like you are already building Xen with this option. So all
looks good for RISC-V. That said, I would suggest to check that
__riscv_cmodel_medany is defined in files where you implement C function
called from early assembly code.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2023-01-09 11:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 13:14 [PATCH v1 0/8] Basic early_printk and smoke test implementation Oleksii Kurochko
2023-01-06 13:14 ` [PATCH v1 1/8] xen/riscv: introduce dummy asm/init.h Oleksii Kurochko
2023-01-06 13:42 ` Julien Grall
2023-01-09 8:53 ` Oleksii
2023-01-06 13:14 ` [PATCH v1 2/8] xen/riscv: introduce asm/types.h header file Oleksii Kurochko
2023-01-06 14:12 ` Jan Beulich
2023-01-09 8:55 ` Oleksii
2023-01-06 13:14 ` [PATCH v1 3/8] xen/riscv: introduce stack stuff Oleksii Kurochko
2023-01-06 13:54 ` Julien Grall
2023-01-09 9:00 ` Oleksii
2023-01-06 14:15 ` Jan Beulich
2023-01-09 8:57 ` Oleksii
2023-01-06 14:55 ` Andrew Cooper
2023-01-06 13:14 ` [PATCH v1 4/8] xen/riscv: introduce sbi call to putchar to console Oleksii Kurochko
2022-12-20 6:23 ` Bobby Eshleman
2023-01-06 17:16 ` Andrew Cooper
2022-12-20 6:50 ` Bobby Eshleman
2023-01-09 13:01 ` Oleksii
2023-01-06 13:40 ` Julien Grall
2023-01-06 15:19 ` Andrew Cooper
2023-01-06 15:39 ` Julien Grall
2023-01-09 9:04 ` Oleksii
2023-01-09 11:11 ` Julien Grall [this message]
2023-01-06 15:19 ` Michal Orzel
2023-01-09 9:06 ` Oleksii
2023-01-06 13:14 ` [PATCH v1 5/8] xen/include: include <asm/types.h> in <xen/early_printk.h> Oleksii Kurochko
2023-01-06 13:45 ` Julien Grall
2023-01-06 13:14 ` [PATCH v1 6/8] xen/riscv: introduce early_printk basic stuff Oleksii Kurochko
2023-01-06 13:51 ` Julien Grall
2023-01-09 9:10 ` Oleksii
2023-01-09 11:14 ` Julien Grall
2023-01-06 13:14 ` [PATCH v1 7/8] xen/riscv: print hello message from C env Oleksii Kurochko
2023-01-06 13:14 ` [PATCH v1 8/8] automation: add RISC-V smoke test Oleksii Kurochko
2023-01-06 15:05 ` Andrew Cooper
2023-01-09 9:11 ` Oleksii
2023-01-06 13:51 ` [PATCH v1 0/8] Basic early_printk and smoke test implementation Andrew Cooper
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=5531505f-b04b-7b70-68da-18d804790c25@xen.org \
--to=julien@xen.org \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=bobbyeshleman@gmail.com \
--cc=connojdavis@gmail.com \
--cc=gianluca@rivosinc.com \
--cc=oleksii.kurochko@gmail.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 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).