Lines Matching refs:TB
12 - Negative addresses such as "-23 TB" are absolute addresses in bytes, counted down
16 For example 0xffffe90000000000 == -23 TB, it's 23 TB lower than the top of the
20 from TB to GB and then MB/KB.
22 - "16M TB" might look weird at first sight, but it's an easier way to visualize size
32 …0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory, different …
35 …0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | ... huge, almost 64 bits wide hole of…
36 … | | | | virtual memory addresses up to the -128 TB
43 …ffff800000000000 | -128 TB | ffff87ffffffffff | 8 TB | ... guard hole, also reserved for hyp…
44 ffff880000000000 | -120 TB | ffff887fffffffff | 0.5 TB | LDT remap for PTI
45 …ffff888000000000 | -119.5 TB | ffffc87fffffffff | 64 TB | direct mapping of all physical memory…
46 ffffc88000000000 | -55.5 TB | ffffc8ffffffffff | 0.5 TB | ... unused hole
47 ffffc90000000000 | -55 TB | ffffe8ffffffffff | 32 TB | vmalloc/ioremap space (vmalloc_base)
48 ffffe90000000000 | -23 TB | ffffe9ffffffffff | 1 TB | ... unused hole
49 ffffea0000000000 | -22 TB | ffffeaffffffffff | 1 TB | virtual memory map (vmemmap_base)
50 ffffeb0000000000 | -21 TB | ffffebffffffffff | 1 TB | ... unused hole
51 ffffec0000000000 | -20 TB | fffffbffffffffff | 16 TB | KASAN shadow memory
57 fffffc0000000000 | -4 TB | fffffdffffffffff | 2 TB | ... unused hole
59 fffffe0000000000 | -2 TB | fffffe7fffffffff | 0.5 TB | cpu_entry_area mapping
60 fffffe8000000000 | -1.5 TB | fffffeffffffffff | 0.5 TB | ... unused hole
61 ffffff0000000000 | -1 TB | ffffff7fffffffff | 0.5 TB | %esp fixup stacks
116 fffffc0000000000 | -4 TB | fffffdffffffffff | 2 TB | ... unused hole
118 fffffe0000000000 | -2 TB | fffffe7fffffffff | 0.5 TB | cpu_entry_area mapping
119 fffffe8000000000 | -1.5 TB | fffffeffffffffff | 0.5 TB | ... unused hole
120 ffffff0000000000 | -1 TB | ffffff7fffffffff | 0.5 TB | %esp fixup stacks