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 S934322AbcIVRaf (ORCPT <rfc822;w@1wt.eu>);
        Thu, 22 Sep 2016 13:30:35 -0400
Received: from Galois.linutronix.de ([146.0.238.70]:38861 "EHLO
        Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1757030AbcIVRad (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 22 Sep 2016 13:30:33 -0400
Date: Thu, 22 Sep 2016 19:28:01 +0200 (CEST)
From: Thomas Gleixner <tglx@linutronix.de>
To: Binoy Jayan <binoy.jayan@linaro.org>
cc: Carsten Emde <C.Emde@osadl.org>,
        "Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
        Ingo Molnar <mingo@redhat.com>,
        Daniel Wagner <daniel.wagner@bmw-carit.de>,
        Arnd Bergmann <arnd@arndb.de>,
        Linux kernel mailing list <linux-kernel@vger.kernel.org>,
        Masami <masami.hiramatsu@linaro.org>,
        Mark Brown <mark.brown@linaro.org>
Subject: Re: [RFC PATCH v7 4/5] tracing: Measure delayed hrtimer offset
 latency
In-Reply-To: <CAHv-k_-yVqZXJeHugoYg0_XmT0Gb14wv0c+DS1qf5PKUhSMcJA@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1609221910060.5599@nanos>
References: <1474379517-7705-1-git-send-email-binoy.jayan@linaro.org> <1474379517-7705-5-git-send-email-binoy.jayan@linaro.org> <alpine.DEB.2.20.1609201609130.6905@nanos> <CAHv-k__757zY9DAihbFga4bGYnYchw7pTnOc_uKhbd9UB6GYdA@mail.gmail.com>
 <alpine.DEB.2.20.1609211720520.5573@nanos> <CAHv-k_-yVqZXJeHugoYg0_XmT0Gb14wv0c+DS1qf5PKUhSMcJA@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Binoy,

On Thu, 22 Sep 2016, Binoy Jayan wrote:
> The condition 'ktime_to_ns(tim) < ktime_to_ns(now)' checks if the timer
> has already expired w.r.t. 'soft timeout' value as it does not include
> the slack value 'delta_ns'. In that case 'tim_expiry' is normalized to
> the current time.

You are halfways coming close to the point why this is done, but your
conclusion is completely wrong.  The correct keyword is "expired", but
anything else is just random speculation.

> (I was under the impression that this inaccuracy
> could be because timer was initially running on a different cpu. If that
> is not the case, I guess we can use the code mentioned below).

We are not playing a guessing game here.
 
> I am using 'hrtimer_get_softexpires_tv64' instead of 'hrtimer_get_expires'
> so that 'latency' is never negative. Please let me know if this looks ok.

No it does not. And it won't look correct until you finally sit down and
decode and understand the functionality behind this code.

I'm not going to continue this, as it's not my job to explain you the code
which you are trying to submit.

I'm not blaming you, but I blame the responsible persons inside your
company who task you with that and expect that I'm going to do their work
of explaining to you how that code works.

@Arnd, @Mark: I'm starting to get seriously grumpy about that.

Thanks,

	tglx