Home
last modified time | relevance | path

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

/linux/Documentation/virt/kvm/
A Dppc-pv.rst153 mfmsr rX ld rX, magic_page->msr
154 mfsprg rX, 0 ld rX, magic_page->sprg0
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
163 mtmsr rX std rX, magic_page->msr
168 mtsrr0 rX std rX, magic_page->srr0
169 mtsrr1 rX std rX, magic_page->srr1
170 mtdar rX std rX, magic_page->dar
[all …]
/linux/arch/powerpc/include/asm/
A Dreg.h1154 #define GET_PACA(rX) \ argument
1156 mfspr rX,SPRN_SPRG_PACA; \
1158 mfspr rX,SPRN_SPRG_HPACA; \
1161 #define SET_PACA(rX) \ argument
1163 mtspr SPRN_SPRG_PACA,rX; \
1168 #define GET_SCRATCH0(rX) \ argument
1175 #define SET_SCRATCH0(rX) \ argument
1183 #define GET_SCRATCH0(rX) mfspr rX,SPRN_SPRG_SCRATCH0 argument
1184 #define SET_SCRATCH0(rX) mtspr SPRN_SPRG_SCRATCH0,rX argument
1199 #define SET_PACA(rX) mtspr SPRN_SPRG_PACA,rX argument
[all …]
/linux/scripts/package/
A Dbuilddeb47 chmod -R a+rX "$pdir"
/linux/Documentation/networking/
A Dfilter.rst1359 id=2 means that two ``r3 += rX`` instructions were seen, so r3 points to some
1366 Operation ``r3 += rX`` may overflow and become less than original skb->data,
1367 therefore the verifier has to prevent that. So when it sees ``r3 += rX``
1368 instruction and rX is more than 16-bit value, any subsequent bounds-check of r3

Completed in 13 milliseconds