Searched refs:rX (Results 1 – 5 of 5) sorted by relevance
/openbmc/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 …]
|
/openbmc/linux/arch/powerpc/include/asm/ |
H A D | reg.h | 1162 #define GET_PACA(rX) \ argument 1164 mfspr rX,SPRN_SPRG_PACA; \ 1166 mfspr rX,SPRN_SPRG_HPACA; \ 1169 #define SET_PACA(rX) \ argument 1171 mtspr SPRN_SPRG_PACA,rX; \ 1173 mtspr SPRN_SPRG_HPACA,rX; \ 1176 #define GET_SCRATCH0(rX) \ argument 1178 mfspr rX,SPRN_SPRG_SCRATCH0; \ 1180 mfspr rX,SPRN_SPRG_HSCRATCH0; \ 1183 #define SET_SCRATCH0(rX) \ argument [all …]
|
/openbmc/linux/scripts/package/ |
H A D | builddeb | 47 chmod -R go-w,a+rX,ug-s "$pdir"
|
/openbmc/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
|
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/uefi/files/ |
H A D | 0001-BootLogoLib-align-logo-coords-to-be-even.patch | 104 z+)+6=LNGygcdmtDFf!*rX~&AiAhCPhO3Yyo*|D0v8r7m846<zE=rt_wom+tqi+s!C
|