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: Thu, 30 Apr 2020 18:04:36 +0200 From: Peter Zijlstra <peterz@...radead.org> To: Marc Zyngier <maz@...nel.org> Cc: Will Deacon <will@...nel.org>, Leo Yan <leo.yan@...aro.org>, Mark Rutland <mark.rutland@....com>, Ingo Molnar <mingo@...hat.com>, Arnaldo Carvalho de Melo <acme@...nel.org>, Alexander Shishkin <alexander.shishkin@...ux.intel.com>, Jiri Olsa <jolsa@...hat.com>, Namhyung Kim <namhyung@...nel.org>, Catalin Marinas <catalin.marinas@....com>, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Mathieu Poirier <mathieu.poirier@...aro.org>, Mike Leach <mike.leach@...aro.org>, Al Grant <Al.Grant@....com>, James Clark <James.Clark@....com>, tglx@...utronix.de Subject: Re: [PATCH] arm64: perf_event: Fix time_offset for arch timer On Thu, Apr 30, 2020 at 04:29:23PM +0100, Marc Zyngier wrote: > I wonder if we could/should make __sched_clock_offset available even when > CONFIG_HAVE_UNSTABLE_SCHED_CLOCK isn't defined. It feels like it would > help with this particular can or worm... Errrgh. __sched_clock_offset is only needed on x86 because we transition from one clock device to another on boot. It really shouldn't exist on anything sane. Let me try and understand your particular problem better.
Powered by blists - more mailing lists