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, 6 Jul 2015 13:45:05 +0900 From: Magnus Damm <magnus.damm@...il.com> To: Geert Uytterhoeven <geert@...ux-m68k.org> Cc: Wolfram Sang <wsa@...-dreams.de>, Thomas Gleixner <tglx@...utronix.de>, Simon Horman <horms@...ge.net.au>, Kevin Hilman <khilman@...nel.org>, Tyler Baker <tyler.baker@...aro.org>, Borislav Petkov <bp@...en8.de>, Geert Uytterhoeven <geert+renesas@...der.be>, Linux-sh list <linux-sh@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock from event handler" Hi Geert, On Sat, Jul 4, 2015 at 2:02 AM, Geert Uytterhoeven <geert@...ux-m68k.org> wrote: > Hi Wolfram, > > On Fri, Jul 3, 2015 at 4:37 PM, Wolfram Sang <wsa@...-dreams.de> wrote: >>> So this is a single core machine and uses the em_sti timer w/o the >>> broadcast nonsense. In Simons case it looks like em_sti is used as >>> broadcast device. >> >> We use the same board. Just my kernel has SMP=n. > > Unlike our other multi-core A9 SoCs, emev2.dtsi doesn't have a node > for the arm,cortex-a9-twd-timer? That's right, the TWD was never enabled on upstream EMEV2. I believe it is documented in the data sheet though, however the actual vendor-specific glue is a bit different compared to other SoCs from Renesas Electronics - this most likely since EMEV2 was initially made by NEC Electronics instead of Renesas. I've been told that it was one of the earlier Cortex-A9 designs around so some special surprises may exist! Cheers, / magnus -- 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