linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sodagudi Prasad <psodagud@codeaurora.org>,
	pasha.tatashin@oracle.com, gregkh@linuxfoundation.org,
	sboyd@codeaurora.org, john.stultz@linaro.org,
	chang-an.chen@mediatek.com, mingo@kernel.org, pmladek@suse.com,
	sergey.senozhatsky@gmail.com, linux-kernel@vger.kernel.org,
	tsoni@codeaurora.org
Subject: Re: sched_clock and device suspend/resume
Date: Wed, 10 Jul 2019 20:35:32 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1907102034190.1758@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20190710113609.7b63c5d6@gandalf.local.home>

On Wed, 10 Jul 2019, Steven Rostedt wrote:

> 
> [ Resending as your Cc was screwed up and caused my reply to mess up
>   the Cc list ]
> 
> On Wed, 10 Jul 2019 08:20:37 -0700
> Sodagudi Prasad <psodagud@codeaurora.org> wrote:
> 
> > Another option is printing the epoch/cycles information in every print 
> > statement similar to thread id or processor id added 
> > recently(CONFIG_PRINTK_CALLER). This can be avoided if we start 
> > accounting suspend time in sched_clock.
> 
> Or another option is add a new clock that printk and tracing can use.
> tracing already can switch between clocks trivially.
> 
> sched_clock_continuous() ? (I know, horrible name), that simply keeps
> track of the time delta at suspend and returns:
> 
> 	sched_clock() + delta;

Which you get already when you do

# echo boot > /sys/kernel/debug/tracing/trace_clock

Thanks,

	tglx

  reply	other threads:[~2019-07-10 18:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1d6ef4687c87dd4d2ec88d0d593a9c1d@codeaurora.org>
2019-07-10 15:36 ` sched_clock and device suspend/resume Steven Rostedt
2019-07-10 18:35   ` Thomas Gleixner [this message]
2019-07-10 18:57     ` Steven Rostedt
2019-07-10 19:06       ` Thomas Gleixner
2019-07-10 19:13         ` Steven Rostedt
2019-07-10 19:15           ` Thomas Gleixner
2019-07-10 19:22             ` Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1907102034190.1758@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=chang-an.chen@mediatek.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=pasha.tatashin@oracle.com \
    --cc=pmladek@suse.com \
    --cc=psodagud@codeaurora.org \
    --cc=rostedt@goodmis.org \
    --cc=sboyd@codeaurora.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tsoni@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).