lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 23 Nov 2015 11:34:58 -0800 From: "Shi, Yang" <yang.shi@...aro.org> To: Z Lim <zlim.lnx@...il.com>, Will Deacon <will.deacon@....com>, Alexei Starovoitov <ast@...nel.org>, "David S. Miller" <davem@...emloft.net> CC: daniel@...earbox.net, Catalin Marinas <catalin.marinas@....com>, Xi Wang <xi.wang@...il.com>, LKML <linux-kernel@...r.kernel.org>, Network Development <netdev@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, linaro-kernel@...ts.linaro.org Subject: Re: [PATCH 1/2] arm64: bpf: add 'store immediate' instruction Hi folks, Any more comments on this patch (store immediate only)? I need more time to add XADD (I'm supposed everyone agrees it is equivalent to atomic_add). However, this one is irrelevant to XADD, so we may be able to apply it first? Thanks, Yang On 11/12/2015 7:45 PM, Z Lim wrote: > On Thu, Nov 12, 2015 at 11:33 AM, Shi, Yang <yang.shi@...aro.org> wrote: >> On 11/11/2015 4:39 AM, Will Deacon wrote: >>> >>> Wait a second, we're both talking rubbish here :) The STR (immediate) >>> form is referring to the addressing mode, whereas this patch wants to >>> store an immediate value to memory, which does need moving to a register >>> first. >> >> >> Yes, the immediate means immediate offset for addressing index. Doesn't mean >> to store immediate to memory. >> >> I don't think any load-store architecture has store immediate instruction. >> > > Indeed. Sorry for the noise. > > Somehow Will caught a whiff of whatever I was smoking then :) > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists