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, 30 Nov 2015 10:03:26 +0800 From: libin <huawei.libin@...wei.com> To: Steven Rostedt <rostedt@...dmis.org> CC: <mingo@...hat.com>, <catalin.marinas@....com>, <will.deacon@....com>, <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>, <guohanjun@...wei.com>, <dingtianhong@...wei.com> Subject: Re: [PATCH] arm64: ftrace: stop using kstop_machine to enable/disable tracing on 2015/11/28 23:58, Steven Rostedt wrote: > On Sat, 28 Nov 2015 15:50:09 +0800 > Li Bin <huawei.libin@...wei.com> wrote: > >> On arm64, kstop_machine which is hugely disruptive to a running >> system is not needed to convert nops to ftrace calls or back, >> because that modifed code is a single 32bit instructions which >> is impossible to cross cache (or page) boundaries, and the used str >> instruction is single-copy atomic. > Is this really true? I thought that arm (and then perhaps arm64) has > some 2 byte instructions. If that's the case it is very well possible > that a 4 byte instruction can cross cache lines. When system in aarch32 state, it will use A32 or T32 instrucion set, and T32 (thumb) have 16-bit instructions. But arm64 that in aarch64 state only using A64 instruction set, which is a clean and fixed length instruction set that instuctions are always 32 bits wide. Right? Thanks, Li Bin > -- Steve > >> Cc: <stable@...r.kernel.org> # 3.18+ >> Signed-off-by: Li Bin <huawei.libin@...wei.com> >> --- >> arch/arm64/kernel/ftrace.c | 5 +++++ >> 1 files changed, 5 insertions(+), 0 deletions(-) > . > -- 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