LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Will Deacon <email@example.com> To: Leo Yan <firstname.lastname@example.org> Cc: Peter Zijlstra <email@example.com>, Marc Zyngier <firstname.lastname@example.org>, Mark Rutland <email@example.com>, Ingo Molnar <firstname.lastname@example.org>, Arnaldo Carvalho de Melo <email@example.com>, Alexander Shishkin <firstname.lastname@example.org>, Jiri Olsa <email@example.com>, Namhyung Kim <firstname.lastname@example.org>, Catalin Marinas <email@example.com>, firstname.lastname@example.org, email@example.com, Mathieu Poirier <firstname.lastname@example.org>, Mike Leach <email@example.com>, Al Grant <Al.Grant@arm.com>, James Clark <James.Clark@arm.com>, firstname.lastname@example.org Subject: Re: [PATCH] arm64: perf_event: Fix time_offset for arch timer Date: Fri, 1 May 2020 16:26:09 +0100 [thread overview] Message-ID: <20200501152609.GA17646@willie-the-truck> (raw) In-Reply-To: <20200501151448.GA9650@leoy-ThinkPad-X240s> On Fri, May 01, 2020 at 11:14:48PM +0800, Leo Yan wrote: > On Thu, Apr 30, 2020 at 05:18:15PM +0100, Will Deacon wrote: > > On Thu, Apr 30, 2020 at 06:04:36PM +0200, Peter Zijlstra wrote: > > > 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. > > > > I think we still transition from jiffies on arm64, because we don't register > > with sched_clock until the timer driver probes. Marc, is that right? > > > > > Let me try and understand your particular problem better. > > > > I think the long and short of it is that userspace needs a way to convert > > the raw counter cycles into a ns value that can be compared against values > > coming out of sched_clock. To do this accurately, I think it needs the > > cycles value at the point when sched_clock was initialised. > > Will's understanding is exactly what I want to resolve in this patch. > > The background info is for the ARM SPE  decoding with perf tool, if > the timestamp is enabled, it uses the generic timer's counter as > timestamp source. SPE trace data only contains the raw counter cycles, > as Will mentioned, the perf tool needs to convert it to a coordinate > value with sched_clock. This is why this patch tries to calculate the > offset between the raw counter's ns value and sched_clock, eventually > this offset value will be used by SPE's decoding code in Perf tool to > calibrate a 'correct' timestamp. > > Based on your suggestions, I will use __sched_clock_offset to resolve > the accuracy issue in patch v2. (I noticed Peter suggested to use a > new API for wrapping clock_data structure, IIUC, __sched_clock_offset > is more straightforward for this case). > > Please correct if I miss anything. Thank you for reviewing and > suggestions! I don't think you can use __sched_clock_offset without selecting HAVE_UNSTABLE_SCHED_CLOCK, and we really don't want to do that just for this. So Peter's idea about exposing what we need is better, although you'll probably need to take care with the switch-over from jiffies. It needs some thought, but one possibility would be to introduce a new variant of sthe ched_clock_register() function that returns the cycle offset, and then we could fish that out of the timer driver. If we're crossing all the 'i's and dotting all the 't's then we'd want to disable the perf userpage if sched_clock changes clocksource too (a bit like we do for the vDSO). Will
next prev parent reply other threads:[~2020-05-01 15:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-20 9:35 [PATCH] arm64: perf_event: Fix time_offset for arch timer Leo Yan 2020-04-01 1:24 ` Leo Yan 2020-04-30 14:58 ` Will Deacon 2020-04-30 15:29 ` Marc Zyngier 2020-04-30 16:04 ` Peter Zijlstra 2020-04-30 16:18 ` Will Deacon 2020-04-30 17:33 ` Marc Zyngier 2020-05-01 15:14 ` Leo Yan 2020-05-01 15:26 ` Will Deacon [this message] 2020-05-01 16:10 ` Leo Yan 2020-05-01 17:13 ` Will Deacon 2020-05-01 15:29 ` Marc Zyngier 2020-04-30 16:27 ` Peter Zijlstra 2020-04-30 16:45 ` Will Deacon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200501152609.GA17646@willie-the-truck \ --email@example.com \ --cc=Al.Grant@arm.com \ --cc=James.Clark@arm.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).