Home
last modified time | relevance | path

Searched refs:TB (Results 1 – 25 of 77) sorted by relevance

1234

/openbmc/linux/Documentation/arch/x86/x86_64/
H A Dmm.rst12 - 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…
[all …]
/openbmc/linux/Documentation/translations/zh_CN/riscv/
H A Dvm-layout.rst47 0000004000000000 | +256 GB | ffffffbfffffffff | ~16M TB | ... 巨大的、几乎64位宽的直到内核映射的-256GB地方
80 0000000000000000 | 0 | 00007fffffffffff | 128 TB | 用户空间虚拟内存，每个内存管理器不同
83 0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | ... 巨大的、几乎64位宽的直到内核映射的-128TB地方
91 ffff8d7ffee00000 | -114.5 TB | ffff8d7ffeffffff | 2 MB | fixmap
92 ffff8d7fff000000 | -114.5 TB | ffff8d7fffffffff | 16 MB | PCI io
93 ffff8d8000000000 | -114.5 TB | ffff8f7fffffffff | 2 TB | vmemmap
94 ffff8f8000000000 | -112.5 TB | ffffaf7fffffffff | 32 TB | vmalloc/ioremap space
95 ffffaf8000000000 | -80.5 TB | ffffef7fffffffff | 64 TB | 直接映射所有物理内存
96 ffffef8000000000 | -16.5 TB | fffffffeffffffff | 16.5 TB | kasan
/openbmc/linux/Documentation/translations/zh_CN/arch/arm64/
H A Dmemory.txt36 分别都有 39-bit (512GB) 或 48-bit (256TB) 的虚拟地址空间。
37 对于页大小为 64KB的配置，仅使用 2 级转换表，有 42-bit (4TB) 的虚拟地址空间，但内存布局相同。
57 0000000000000000 0000ffffffffffff 256TB 用户空间
58 ffff000000000000 ffffffffffffffff 256TB 内核空间
65 0000000000000000 000003ffffffffff 4TB 用户空间
66 fffffc0000000000 ffffffffffffffff 4TB 内核空间
73 0000000000000000 0000ffffffffffff 256TB 用户空间
74 ffff000000000000 ffffffffffffffff 256TB 内核空间
/openbmc/linux/Documentation/translations/zh_TW/arch/arm64/
H A Dmemory.txt40 分別都有 39-bit (512GB) 或 48-bit (256TB) 的虛擬地址空間。
41 對於頁大小爲 64KB的配置，僅使用 2 級轉換表，有 42-bit (4TB) 的虛擬地址空間，但內存布局相同。
61 0000000000000000 0000ffffffffffff 256TB 用戶空間
62 ffff000000000000 ffffffffffffffff 256TB 內核空間
69 0000000000000000 000003ffffffffff 4TB 用戶空間
70 fffffc0000000000 ffffffffffffffff 4TB 內核空間
77 0000000000000000 0000ffffffffffff 256TB 用戶空間
78 ffff000000000000 ffffffffffffffff 256TB 內核空間
/openbmc/qemu/docs/devel/
H A Dtcg.rst26 Block (TB). If the state changes (e.g. privilege level), a new TB will
27 be generated and the previous TB won't be used anymore until the state
28 matches the state recorded in the previous TB. The same idea can be applied
41 current TB, going through the TB epilogue, and then back to the
42 main loop. That’s where QEMU looks for the next TB to execute,
44 in memory. Then QEMU proceeds to execute this next TB, starting at the
47 Exiting from the TB this way will cause the ``cpu_exec_interrupt()``
52 In order to accelerate the cases where the TB for the new
61 ``helper_lookup_tb_ptr``. This helper will look for an existing TB that
62 matches the current CPU state. If the destination TB is available its
[all …]
/openbmc/linux/Documentation/riscv/
H A Dvm-layout.rst42 …0000004000000000 | +256 GB | ffffffbfffffffff | ~16M TB | ... huge, almost 64 bits wide hole of…
75 …0000000000000000 | 0 | 00007fffffffffff | 128 TB | user-space virtual memory, different …
78 …0000800000000000 | +128 TB | ffff7fffffffffff | ~16M TB | ... huge, almost 64 bits wide hole of…
79 … | | | | virtual memory addresses up to the -128 TB
86 ffff8d7ffea00000 | -114.5 TB | ffff8d7ffeffffff | 6 MB | fixmap
87 ffff8d7fff000000 | -114.5 TB | ffff8d7fffffffff | 16 MB | PCI io
88 ffff8d8000000000 | -114.5 TB | ffff8f7fffffffff | 2 TB | vmemmap
89 ffff8f8000000000 | -112.5 TB | ffffaf7fffffffff | 32 TB | vmalloc/ioremap space
90 … ffffaf8000000000 | -80.5 TB | ffffef7fffffffff | 64 TB | direct mapping of all physical memory
91 ffffef8000000000 | -16.5 TB | fffffffeffffffff | 16.5 TB | kasan
/openbmc/linux/arch/x86/crypto/
H A Dsha1_avx2_x86_64_asm.S105 .set TB, REG_TB define
327 .set B, TB
328 .set TB, A define
357 mov B, TB
360 andn D, TB, T1
361 and C, TB
362 xor T1, TB
389 rorx $(32-30),A, TB /* b>>>2 for next round */
410 rorx $(32-30), A, TB /* b>>>2 for next round */
435 rorx $(32-30), A, TB /* b>>>2 for next round */
[all …]
/openbmc/linux/Documentation/arch/arm64/
H A Dmemory.rst13 (256TB) virtual addresses, respectively, for both user and kernel. With
14 64KB pages, only 2 levels of translation tables, allowing 42-bit (4TB)
33 0000000000000000 0000ffffffffffff 256TB user
34 ffff000000000000 ffff7fffffffffff 128TB kernel logical memory map
35 [ffff600000000000 ffff7fffffffffff] 32TB [kasan shadow region]
37 ffff800080000000 fffffbffefffffff 124TB vmalloc
42 fffffc0000000000 fffffdffffffffff 2TB vmemmap
43 fffffe0000000000 ffffffffffffffff 2TB [guard region]
52 [fffd800000000000 ffff7fffffffffff] 512TB [kasan shadow region]
54 ffff800080000000 fffffbffefffffff 124TB vmalloc
[all …]
/openbmc/linux/Documentation/admin-guide/device-mapper/
H A Dzero.rst21 desired size of the sparse device. For this example, we'll assume a 10TB
24 TEN_TERABYTES=`expr 10 \* 1024 \* 1024 \* 1024 \* 2` # 10 TB in sectors
35 This will create a 10TB sparse device called /dev/mapper/sparse1 that has
/openbmc/openbmc/meta-yadro/meta-nicole/recipes-phosphor/host/op-proc-control/
H A D0001-Stop-and-send-SRESET-for-one-thread-only.patch12 [ 235.694220] watchdog: CPU 97 TB:187362511366, last heartbeat TB:159120095297 (55160ms ago)
/openbmc/linux/drivers/net/fddi/skfp/
H A Dpcmplc.c245 (np == PB) ? TB : TM ; in pcm_init()
262 mib->fddiPORTMy_Type = (np == PB) ? TB : TA ; in pcm_init()
330 case TB : in pcm_init()
1270 mib->fddiPORTNeighborType = TB ; in pc_rcode_actions()
1407 if (mib->fddiPORTMy_Type == TB || mib->fddiPORTMy_Type == TM) in pc_tcode_actions()
1426 ((policy & POLICY_AB) && ne == TB) || in pc_tcode_actions()
1431 case TB : in pc_tcode_actions()
1434 ((policy & POLICY_BB) && ne == TB) || in pc_tcode_actions()
1442 ((policy & POLICY_SB) && ne == TB) || in pc_tcode_actions()
1450 ((policy & POLICY_MB) && ne == TB) || in pc_tcode_actions()
[all …]
H A Dcfm.c68 TNONE,TB,TB,TS,
69 TA,TB,TS,TB
122 case TB: in selection_criteria()
/openbmc/qemu/tests/qemu-iotests/
H A D084.out20 Test 1: Maximum size (512 TB - 128 MB):
26 Test 2: Size too large (512 TB - 128 MB + 64 kB)
H A D213.out90 Job failed: Image size too large; max of 64TB
96 Job failed: Image size too large; max of 64TB
102 Job failed: Image size too large; max of 64TB
108 Job failed: Image size too large; max of 64TB
/openbmc/linux/drivers/net/fddi/skfp/h/
H A Dsmtstate.h44 #define TB 1 macro
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A Dpipeline.dot4 rankdir=TB
/openbmc/linux/Documentation/admin-guide/media/
H A Drkisp1.dot2 rankdir=TB
H A Dvimc.dot4 rankdir=TB
/openbmc/linux/tools/perf/Documentation/
H A Dperf-bench.txt164 Available units are B, KB, MB, GB and TB (case insensitive).
188 Available units are B, KB, MB, GB and TB (case insensitive).
/openbmc/linux/fs/unicode/
H A Dutf8-norm.c249 #define TB (0x11A7) macro
286 h += utf8encode3((char *)h, ti + TB); in utf8hangul()
/openbmc/u-boot/disk/
H A DKconfig19 bootloader. Note 2TB partition limit; see
82 common when EFI is the bootloader. Note 2TB partition limit;
/openbmc/linux/Documentation/translations/zh_CN/dev-tools/
H A Dkasan.rst247 通用KASAN将1/8的内核内存专用于其影子内存（16TB以覆盖x86_64上的128TB），并使用
/openbmc/qemu/target/riscv/insn_trans/
H A Dtrans_rvzawrs.c.inc30 * So let's just exit TB and return to the main loop.
/openbmc/qemu/tcg/
H A Dtcg-ldst.c.inc24 * Generate TB finalization at the end of block
/openbmc/qemu/tests/tcg/multiarch/
H A Dnoexec.c.inc95 /* Trigger TB creation in order to test invalidation. */

1234