linux-kernel - Re: [PATCH] ufs: core: ufshcd: use CLOCK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAGaU9a_Tm_awy+EAaYpv1Aj+URKkrD1yZDY2dWbhoWj0qUr5uw@mail.gmail.com>
Date:   Mon, 1 Aug 2022 11:23:42 +0800
From:   Stanley Chu <chu.stanley@...il.com>
To:     Daniil Lunev <dlunev@...omium.org>
Cc:     Adrian Hunter <adrian.hunter@...el.com>,
        Bart Van Assche <bvanassche@....org>,
        Alim Akhtar <alim.akhtar@...sung.com>,
        Avri Altman <avri.altman@....com>,
        Bean Huo <beanhuo@...ron.com>,
        Daejun Park <daejun7.park@...sung.com>,
        "James E.J. Bottomley" <jejb@...ux.ibm.com>,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH] ufs: core: ufshcd: use CLOCK_BOOTTIME for debugging timestamps

Hi Daniil,

On Wed, Jul 20, 2022 at 6:49 PM Daniil Lunev <dlunev@...omium.org> wrote:
>
> CLOCK_MONOTONIC is not advanced when the system is in suspend. This
> becomes problematic when debugging issues related to suspend-resume:
> the timestamps printed by ufshcd_print_trs can not be correlated with
> dmesg entries, which are timestamped with CLOCK_BOOTTIME.
>
> This CL changes the used clock to CLOCK_BOOTTIME for the informational
> timestamp variables and adds mirroring CLOCK_BOOTIME instances for
> variables used in subsequent derevations (to not change the semantics of
> those derevations).
>
> Signed-off-by: Daniil Lunev <dlunev@...omium.org>
>

Regarding the suspend/resume issue breakdown with aligned timestamp
with the dmesg logs, perhaps we need to use "sched_clock()" since it
is the timestamp used by dmesg?

Thanks,
Stanley