linux-kernel - Re: [PATCH 7/7] trace: Update documentation for mono, mono

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAJWu+opzu=J0=6FJvVQUWuQ1frzcJxRtADxp4ULZ_e1pm6bFUA@mail.gmail.com>
Date:   Tue, 29 Nov 2016 08:10:30 -0800
From:   Joel Fernandes <joelaf@...gle.com>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     John Stultz <john.stultz@...aro.org>,
        lkml <linux-kernel@...r.kernel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        Richard Cochran <richardcochran@...il.com>,
        Prarit Bhargava <prarit@...hat.com>
Subject: Re: [PATCH 7/7] trace: Update documentation for mono, mono_raw and
 boot clock

On Mon, Nov 28, 2016 at 11:26 PM, Ingo Molnar <mingo@...nel.org> wrote:
>
> * John Stultz <john.stultz@...aro.org> wrote:
>
>> +       boot: This is the boot clock (CLOCK_BOOTTIME) and is based on the
>> +             fast monotonic clock, but also accounts for time spent in
>> +             suspend. Since the clock access is designed for use in
>> +             tracing in the suspend path, some side effects are possible
>> +             if clock is accessed after the suspend time is accounted before
>> +             the fast mono clock is updated. In this case, the clock update
>> +             appears to happen slightly sooner than it normally would have.
>> +             Also on 32-bit systems, its possible that the 64-bit boot offset
>> +             sees a partial update. These effects are rare and post
>> +             processing should be able to handle them. See comments on
>> +             ktime_get_boot_fast_ns function for more information.
>
> s/its possible/it's possible
> s/comments on ktime_get_boost_fast_ns function/comments in the ktime_get_boost_fast_ns() function
>

Thanks, I'll fix these up and repost.

Regards,
Joel

> Thanks,
>
>         Ingo