From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1753183AbdGJASu (ORCPT <rfc822;w@1wt.eu>);
        Sun, 9 Jul 2017 20:18:50 -0400
Received: from mail.kernel.org ([198.145.29.99]:38226 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753133AbdGJASt (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 9 Jul 2017 20:18:49 -0400
DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 77D0022B4E
Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org
Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=mhiramat@kernel.org
Date: Mon, 10 Jul 2017 09:18:45 +0900
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arun Kalyanasundaram <arunkaly@google.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, mhiramat@kernel.org,
        linux-kernel@vger.kernel.org, mingo@kernel.org,
        David Carrillo-Cisneros <davidcc@google.com>
Subject: Re: tracing/kprobes: [Bug] Identical timestamps on two kprobes that
 are few instructions apart
Message-Id: <20170710091845.5db494f938a1ab6c8e2b0259@kernel.org>
In-Reply-To: <CAGjB_BpcrHaRuWQdCmP8_H6k2JUgSwQAt1tm9Kxnm6CyMOc_Ng@mail.gmail.com>
References: <CAGjB_BpTmk+gvNMpuxWweu1UnzFixPrxKKAxzJxm2svz+-FVXg@mail.gmail.com>
        <20170707150136.7f167b85@gandalf.local.home>
        <CAGjB_BpcrHaRuWQdCmP8_H6k2JUgSwQAt1tm9Kxnm6CyMOc_Ng@mail.gmail.com>
X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hello Arun,

On Fri, 7 Jul 2017 16:06:40 -0700
Arun Kalyanasundaram <arunkaly@google.com> wrote:

> Hi Steven,
> 
> Thank you very much for your reply. I am using kernel - v4.12-rc3.
> 
> I did something like this and see the issue:
> # trace-cmd record -e kprobes:s1 -e kprobes:s2 -- taskset -c 0 my_program
> # ./trace-cmd report -t --cpu 0
> 
> The issue is pretty intermittent and only happens when there are a lot
> of samples, and so "my_program" generates a few hundred threads. Any
> pointers on debugging this would be very helpful, or please let me
> know if you want me to collect any log messages.

Ok, so this happens with ftrace+trace-cmd too.
If you run it on x86-64, could you add "-C x86-tsc" and check still
it happens? If not, I guess it happens when it adjusts timestamp.

Thank you,

-- 
Masami Hiramatsu <mhiramat@kernel.org>