Home
last modified time | relevance | path

Searched refs:TSB (Results 1 – 4 of 4) sorted by relevance

/arch/sparc/include/asm/
A Dtsb.h77 #define TSB_LOAD_QUAD(TSB, REG) \ argument
86 661: lduwa [TSB] ASI_N, REG; \
92 #define TSB_LOAD_TAG(TSB, REG) \ argument
93 661: ldxa [TSB] ASI_N, REG; \
96 ldxa [TSB] ASI_PHYS_USE_EC, REG; \
121 99: TSB_LOAD_TAG_HIGH(TSB, REG1); \
131 #define TSB_WRITE(TSB, TTE, TAG) \ argument
132 add TSB, 0x8, TSB; \
133 TSB_STORE(TSB, TTE); \
134 sub TSB, 0x8, TSB; \
[all …]
/arch/sparc/kernel/
A Ddtlb_miss.S3 ldxa [%g0] ASI_DMMU_TSB_8KB_PTR, %g1 ! Get TSB 8K pointer
9 TSB_LOAD_QUAD(%g1, %g4) ! Load TSB entry
A Ditlb_miss.S3 ldxa [%g0] ASI_IMMU_TSB_8KB_PTR, %g1 ! Get TSB 8K pointer
9 TSB_LOAD_QUAD(%g1, %g4) ! Load TSB entry
/arch/arm64/
A DKconfig907 bool "Cortex-A710: 2054223: workaround TSB instruction failing to flush trace"
913 Affected cores may fail to flush the trace data on a TSB instruction, when
917 Workaround is to issue two TSB consecutively on affected cores.
922 bool "Neoverse-N2: 2067961: workaround TSB instruction failing to flush trace"
928 Affected cores may fail to flush the trace data on a TSB instruction, when
932 Workaround is to issue two TSB consecutively on affected cores.
1003 Work around this in the driver by executing TSB CSYNC and DSB after collection

Completed in 8 milliseconds