| 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
| ||
|
Message-ID: <54BD41D3.7030703@gmail.com> Date: Mon, 19 Jan 2015 20:41:39 +0300 From: Dmitry Osipenko <digetx@...il.com> To: Stephen Warren <swarren@...dotorg.org>, Thierry Reding <thierry.reding@...il.com> CC: Alexandre Courbot <gnurou@...il.com>, Peter De Schrijver <pdeschrijver@...dia.com>, linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org, stable@...r.kernel.org Subject: Re: [PATCH] ARM: tegra20: Store CPU "resettable" status in IRAM 19.01.2015 20:26, Stephen Warren пишет: > Hopefully this works out. I suppose it's unlikely anyone will be running code on > the AVP upstrem, so any potential conflict with AVP's usage of IRAM isn't likely > to occur. > I don't see how it can conflict with AVP code. First KB of IRAM is reserved for reset handler. Am I missing something? From reset.h: /* The first 1K of IRAM is permanently reserved for the CPU reset handler */ > __tegra20_cpu1_resettable_status_offset has a lot of _ at the start. Should the > symbol be named more normally? I guess at least it's consistent with the > existing very "underscory" __tegra_cpu_reset_handler_start. I also wasn't happy with "underscory" :) And yes, I left it for consistency. Please feel free to rename it, if needed. -- Dmitry -- 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