From: Stafford Horne <shorne@gmail.com>
To: QEMU Development <qemu-devel@nongnu.org>
Cc: Openrisc <openrisc@lists.librecores.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Stafford Horne <shorne@gmail.com>
Subject: [RFC PATCH 0/3] OpenRISC Semihosting and Virt
Date: Sat, 28 May 2022 02:27:27 +0900 [thread overview]
Message-ID: <20220527172731.1742837-1-shorne@gmail.com> (raw)
Hello,
I provide 2 options here 2 help with OpenRISC CI testing sush as the wireguard
testing that Jason has been working on.
The two are:
1. Add semihosting to openrisc to handle l.nop based Halt and Reset
2. Define a new virt platform, this includes widing in the sifive test device
that provides a syscon interface to allow for shutdown and reboot.
We could upstream both of them or just one. I am leaning toward dropping the
semi-hosting work and just going ahead with virt.
The semi-hosting stuff was discussed here:
- https://www.mail-archive.com/qemu-devel@nongnu.org/msg884560.html
Also, I started to propose architecture changes here:
- https://github.com/openrisc/openrisc.github.io/pull/18
However, looking at how other platforms define semihosting it seems the openrisc
requirements are quite different. We do not use the open/close/write etc
syscalls as riscv, arm etc do.
Stafford Horne (3):
target/openrisc: Add basic support for semihosting
hw/openrisc: Split re-usable boot time apis out to boot.c
hw/openrisc: Add the OpenRISC virtual machine
configs/devices/or1k-softmmu/default.mak | 3 +
hw/openrisc/Kconfig | 9 +
hw/openrisc/boot.c | 127 +++++++
hw/openrisc/meson.build | 2 +
hw/openrisc/openrisc_sim.c | 106 +-----
hw/openrisc/virt.c | 429 +++++++++++++++++++++++
include/hw/openrisc/boot.h | 34 ++
qemu-options.hx | 16 +-
target/openrisc/cpu.h | 2 +
target/openrisc/helper.h | 1 +
target/openrisc/meson.build | 1 +
target/openrisc/openrisc-semi.c | 54 +++
target/openrisc/sys_helper.c | 5 +
target/openrisc/translate.c | 6 +
14 files changed, 690 insertions(+), 105 deletions(-)
create mode 100644 hw/openrisc/boot.c
create mode 100644 hw/openrisc/virt.c
create mode 100644 include/hw/openrisc/boot.h
create mode 100644 target/openrisc/openrisc-semi.c
--
2.31.1
next reply other threads:[~2022-05-27 17:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 17:27 Stafford Horne [this message]
2022-05-27 17:27 ` [RFC PATCH 1/3] target/openrisc: Add basic support for semihosting Stafford Horne
2022-06-02 15:39 ` Richard Henderson
2022-06-05 0:57 ` Stafford Horne
2022-06-05 14:36 ` Richard Henderson
2022-05-27 17:27 ` [RFC PATCH 2/3] hw/openrisc: Split re-usable boot time apis out to boot.c Stafford Horne
2022-06-02 15:40 ` Richard Henderson
2022-05-27 17:27 ` [RFC PATCH 3/3] hw/openrisc: Add the OpenRISC virtual machine Stafford Horne
2022-06-02 11:42 ` Joel Stanley
2022-06-02 15:49 ` Richard Henderson
2022-06-02 19:08 ` Geert Uytterhoeven
2022-06-02 19:59 ` Stafford Horne
2022-06-03 7:05 ` Geert Uytterhoeven
2022-06-05 1:58 ` Stafford Horne
2022-06-05 7:32 ` Stafford Horne
2022-06-05 8:19 ` Jason A. Donenfeld
2022-06-07 9:48 ` Jason A. Donenfeld
2022-06-07 8:11 ` Geert Uytterhoeven
2022-06-07 8:42 ` Arnd Bergmann
2022-06-07 9:47 ` Stafford Horne
2022-06-07 10:04 ` Arnd Bergmann
2022-06-07 10:43 ` Peter Maydell
2022-06-07 12:12 ` Stafford Horne
2022-06-07 14:08 ` Arnd Bergmann
2022-06-05 2:36 ` Stafford Horne
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=20220527172731.1742837-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=Jason@zx2c4.com \
--cc=openrisc@lists.librecores.org \
--cc=qemu-devel@nongnu.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).