1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
# Notes on the implementation of virtual memory
[vmem_types.sail](../model/core/vmem_types.sail) contains type
definitions for the core types used in the virtual memory
specification. The primary vmem specification code is in
[vmem.sail](../model/sys/vmem.sail).
[vmem_pte.sail](../model/sys/vmem_pte.sail) describes page
table entries, processing them for validity and permissions checks,
and their updates. [vmem_ptw.sail](../model/sys/vmem_ptw.sail)
describes page table walk exceptions.
[vmem_tlb.sail](../model/sys/vmem_tlb.sail) implements a
simple TLB (Translation Look-Aside Buffer). Although TLBs are not
specified by RISC-V architecture, it is useful to model at least a
minimal TLB so that we can demonstrate and test `SFENCE.VMA`
functionality (without TLBs, `SFENCE.VMA` is a no-op and there's
nothing to test).
TLBs are also useful for simulation speed. Without a TLB, every Fetch
and Load/Store/AMO in virtual memory mode requires a full page table
walk. Speed matters mostly for large simulations (e.g., Linux-boot
can speed up from tens of minutes to a few minutes).
The main code in [vmem.sail](../model/sys/vmem.sail) is
structured and commented to make it is easy to ignore/skip TLB-related
parts.
## Simplified call graph
The following figure shows a rough call graph, and this can serve as a
guide for understanding the code.
The yellow rectangle(s) represent the code in
[vmem.sail](../model/sys/vmem.sail), and the grey rectangle(s)
represent the code in
[vmem_tlb.sail](../model/sys/vmem_tlb.sail). In each case,
the lighter outer rectangle shows the publicly visible API, and the
darker inner rectangle shows internal (private) resources.
On the left are shown the external places from which the virtual
memory code is invoked, using its public API. On the right are shown
the external resources used by the vmem code.
The main flow (ignoring TLBs) is at the top: The external execution
code for instruction fetch, load, store and AMO invoke
`translateAddr()` and receive a result of `TR_Result` type.
`translateAddr()`, in turn, invokes `translate()`,
`translate_TLB_miss()` and `pt_walk()`; the latter invokes the
`mem_read_priv()` (from [mem.sail](../model/sys/mem.sail)) to
read PTEs (Page Table Entries) from memory. The `SATP` register lives
in [vmem.sail](../model/sys/vmem.sail) and is accessed by the
general `readCSR()` and `writeCSR()` functions.
`translate()` invokes `lookup_TLB()` and, if a hit, invokes
`translate_TLB_hit()`, avoiding a page-table walk (and therefore no
reads from memory).
`mem_write_value_priv()` (from
[mem.sail](../model/sys/mem.sail)) is called for writing back,
to memory, PTEs (Page Table Entries) whose A and/or D bits have been
modified as part of the access.
|
