Searched refs:rX (Results 1 – 3 of 3) sorted by relevance
| /linux/Documentation/virt/kvm/ |
| H A D | ppc-pv.rst | 84 ld rX, -4096(0)
153 mfmsr rX ld rX, magic_page->msr
154 mfsprg rX, 0 ld rX, magic_page->sprg0
155 mfsprg rX, 1 ld rX, magic_page->sprg1
156 mfsprg rX, 2 ld rX, magic_page->sprg2
157 mfsprg rX, 3 ld rX, magic_page->sprg3
158 mfsrr0 rX ld rX, magic_page->srr0
159 mfsrr1 rX ld rX, magic_page->srr1
160 mfdar rX ld rX, magic_page->dar
161 mfdsisr rX lwz rX, magic_page->dsisr
[all …]
|
| /linux/arch/powerpc/include/asm/ |
| H A D | reg.h | 1149 #define GET_PACA(rX) \ argument
1151 mfspr rX,SPRN_SPRG_PACA; \
1153 mfspr rX,SPRN_SPRG_HPACA; \
1156 #define SET_PACA(rX) \ argument
1158 mtspr SPRN_SPRG_PACA,rX; \
1160 mtspr SPRN_SPRG_HPACA,rX; \
1163 #define GET_SCRATCH0(rX) \ argument
1165 mfspr rX,SPRN_SPRG_SCRATCH0; \
1167 mfspr rX,SPRN_SPRG_HSCRATCH0; \
1170 #define SET_SCRATCH0(rX) \ argument
[all …]
|
| /linux/Documentation/bpf/ |
| H A D | verifier.rst | 256 id=2 means that two ``r3 += rX`` instructions were seen, so r3 points to some
263 Operation ``r3 += rX`` may overflow and become less than original skb->data,
264 therefore the verifier has to prevent that. So when it sees ``r3 += rX``
265 instruction and rX is more than 16-bit value, any subsequent bounds-check of r3
|