[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <60a85241-4c51-bab8-6470-354a18fa2e17@gmail.com>
Date: Mon, 5 Dec 2016 20:01:51 -0800
From: David Ahern <dsahern@...il.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Jiri Olsa <jolsa@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Andi Kleen <andi@...stfloor.org>,
Minchan Kim <minchan@...nel.org>
Subject: Re: [PATCH 03/10] perf sched timehist: Handle zero sample->tid
properly
On 12/5/16 7:59 PM, Namhyung Kim wrote:
> No, I didn't investigate it yet. Looking at the original code, you
> seemed to have same issue and workaround like checking prev_pid or
> callchains, right?
most likely. As I responded on another patch, the sched timehist command has been used for years on a range of OS'es and kernel versions. Most of the oddities you see are (sometime quick) fixes to strange differences in kernel versions.
Powered by blists - more mailing lists