From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752187AbcLFEC4 (ORCPT ); Mon, 5 Dec 2016 23:02:56 -0500 Received: from mail-pf0-f195.google.com ([209.85.192.195]:33644 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751598AbcLFECy (ORCPT ); Mon, 5 Dec 2016 23:02:54 -0500 Subject: Re: [PATCH 03/10] perf sched timehist: Handle zero sample->tid properly To: Namhyung Kim References: <20161206034010.6499-1-namhyung@kernel.org> <20161206034010.6499-4-namhyung@kernel.org> Cc: Arnaldo Carvalho de Melo , Ingo Molnar , Peter Zijlstra , Jiri Olsa , LKML , Andi Kleen , Minchan Kim From: David Ahern Message-ID: <60a85241-4c51-bab8-6470-354a18fa2e17@gmail.com> Date: Mon, 5 Dec 2016 20:01:51 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.