From: Thomas Gleixner <tglx@linutronix.de>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "Li, Aubrey" <aubrey.li@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
"Brown, Len" <len.brown@intel.com>,
"alan@linux.intel.com" <alan@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v3]PM/Sleep: Timer quiesce in freeze state
Date: Mon, 26 Jan 2015 15:24:27 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1501261523370.5526@nanos> (raw)
In-Reply-To: <2137807.aqSxQQCuJ3@vostro.rjw.lan>
On Mon, 26 Jan 2015, Rafael J. Wysocki wrote:
> On Monday, January 26, 2015 10:40:24 AM Thomas Gleixner wrote:
> > The only remaining issue might be a NMI calling into
> > ktime_get_mono_fast_ns() before timekeeping is resumed. Its probably a
> > non issue on x86/tsc, but it might be a problem on other platforms
> > which turn off devices, clocks, It's not rocket science to prevent
> > that.
>
> I don't see any users of ktime_get_mono_fast_ns() at all, unless some non-trivial
> macros are involved. At least grepping for it only returns the definition,
> declarations and the line in trace.c.
You can trace in NMI and perf is going to use ktime_get_mono_fast_ns()
eventually as well.
Thanks,
tglx
next prev parent reply other threads:[~2015-01-26 14:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 3:01 [PATCH v3]PM/Sleep: Timer quiesce in freeze state Li, Aubrey
2015-01-14 0:24 ` Li, Aubrey
2015-01-19 15:24 ` Rafael J. Wysocki
2015-01-22 10:15 ` Thomas Gleixner
2015-01-26 8:44 ` Li, Aubrey
2015-01-26 9:40 ` Thomas Gleixner
2015-01-26 14:21 ` Rafael J. Wysocki
2015-01-26 14:15 ` Thomas Gleixner
2015-01-26 14:45 ` Rafael J. Wysocki
2015-01-27 7:12 ` Li, Aubrey
2015-01-26 14:41 ` Rafael J. Wysocki
2015-01-26 14:24 ` Thomas Gleixner [this message]
2015-01-26 14:50 ` Rafael J. Wysocki
2015-01-26 14:34 ` Thomas Gleixner
2015-01-26 15:04 ` Rafael J. Wysocki
2015-01-27 8:03 ` Li, Aubrey
2015-01-27 15:10 ` Rafael J. Wysocki
2015-01-28 0:17 ` Li, Aubrey
2015-01-29 22:20 ` Rafael J. Wysocki
2015-02-06 1:20 ` [Update] " Rafael J. Wysocki
2015-02-06 16:14 ` Peter Zijlstra
2015-02-06 18:29 ` Peter Zijlstra
2015-02-06 22:36 ` Rafael J. Wysocki
2015-02-09 9:49 ` Peter Zijlstra
2015-02-09 14:50 ` Rafael J. Wysocki
2015-02-09 2:54 ` [Update 2x] " Rafael J. Wysocki
2015-02-09 15:20 ` Peter Zijlstra
2015-02-09 15:44 ` Peter Zijlstra
2015-02-09 23:57 ` Rafael J. Wysocki
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.11.1501261523370.5526@nanos \
--to=tglx@linutronix.de \
--cc=alan@linux.intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
/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