(no commit message)
[libreriscv.git] / nlnet_2021_3mdeb_cavatools.mdwn
1 ## Project name
2
3 Libre-SOC 3mdeb Cavatools: Power ISA Simulator
4
5 ## Website / wiki
6
7 <https://libre-soc.org/nlnet_2021_3mdeb_cavatools>
8
9 Please be short and to the point in your answers; focus primarily on
10 the what and how, not so much on the why. Add longer descriptions as
11 attachments (see below). If English isn't your first language, don't
12 worry - our reviewers don't care about spelling errors, only about
13 great ideas. We apologise for the inconvenience of having to submit in
14 English. On the up side, you can be as technical as you need to be (but
15 you don't have to). Do stay concrete. Use plain text in your reply only,
16 if you need any HTML to make your point please include this as attachment.
17
18 ## Abstract: Can you explain the whole project and its expected outcome(s).
19
20 Cavatools is currently a high performance user-operated simulator of
21 the RISC-V ISA. The primary objective of the project is to extend it to
22 implement the scalar Power ISA and the Libre-SOC Draft SVP64
23 Extensions. This will allow rapid prototyping of Extensions to the
24 Power ISA long before they reach silicon (which is very costly).
25 In turn this helps Libre-SOC to deliver on its commitment to provide
26 user-trustable processors for use in Internet routers, desktop,
27 smartphone and other user-operated devices where security and transparency
28 is expected.
29
30 # Have you been involved with projects or organisations relevant to this project before? And if so, can you tell us a bit about your contributions?
31
32 3mdeb is currently helping Libre-SOC with the (horribly slow,
33 easy-to-read) Libre-SOC Power ISA Simulator which is 20,000 times
34 slower than cavatools. 3mdeb is also helping with ISA level unit tests in
35 Libre-SOC's code base that will be used to cross-validate a huge range of
36 Power ISA simulators and actual silicon implementations.
37
38 # Requested Amount
39
40 EUR $50,000.
41
42 # Explain what the requested budget will be used for?
43
44 * To create a compiler which takes Libre-SOC Machine-readable
45 Power ISA specification files and generate c code
46 * To extend cavatools to include support for the Scalar
47 parts of the Power ISA
48 * To then add support for Libre-SOC's Draft SVP64 Extensions
49 * To enhance it to include gdb "remote" machine interface
50 support
51 * To add Power ISA RADIX MMU emulation
52 * To extend cavatools to run a very basic linux
53 initramfs in-memory with basic serial console access
54 * To demonstrate running first a single core linux kernel
55 and later a SMP one, with busybox
56 * To use the exact same Specification c compiler to create
57 an "illegal instruction trap" emulator, integrated
58 into the linux kernel, for emulating Power ISA SIMD instructions
59 (extending the existing trap-and-emulate code already present
60 in ppc64 linux kernel source code)
61
62 # Does the project have other funding sources, both past and present?
63
64 Although there is NLnet funding for the Libre-SOC Simulator
65 (written in python) and associayed unit tests, cavatools, which is
66 written in c by Peter Hsu, does not have funding for the Power ISA
67 aditions.
68
69 # Compare your own project with existing or historical efforts.
70
71 Although there are quite a few Power ISA simulators, none of them
72 are up-to-date or are suited to high performance, like cavatools.
73 cavatools is multi-process and extremely fast, using relatively little
74 memory, where power-gem5, which has a different focus, uses vast amounts
75 of memory and is much slower.
76 DolphinPC and pearpc are over 15 years old and were targetted at 32 bit
77 emulation of much older Power ISA processors. Libre-SOC's python-based
78 simulator only achieves aroubd 2,000 instructions per second on
79 high performance hardware whereas
80 cavatools achieves 200,000 instructions per second per processor
81 on modest hardware.
82 IBM's own Power ISA simulator is proprietary and, because it contains
83 confidential experimentation internal to IBM, may not be made public.
84
85 ## What are significant technical challenges you expect to solve during the project, if any?
86
87 This is at its heart a compiler project, which can be a challenging
88 area. However the language being implemented is quite small and limited,
89 so the project is relatively straightforward.
90
91 ## Describe the ecosystem of the project, and how you will engage with relevant actors and promote the outcomes?
92
93 The project will be developed entirely publicly and transparently,
94 using Libre-SOC Project Resources which are already set up for trustable
95 auditability and transparency.
96
97 Online conferences and talks will be given as progress
98 is made, as well as
99
100 # Extra info to be submitted