From: Borislav Petkov <bp@alien8.de>
To: Stephane Gasparini <stephane.gasparini@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Len Brown <lenb@kernel.org>,
x86@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH] x86: Calculate MHz using APERF/MPERF for cpuinfo and scaling_cur_freq
Date: Fri, 1 Apr 2016 11:50:05 +0200 [thread overview]
Message-ID: <20160401095005.GA25313@pd.tnic> (raw)
In-Reply-To: <7239BF36-2C27-4325-A5B8-01BC4CA58B4C@linux.intel.com>
On Fri, Apr 01, 2016 at 11:30:48AM +0200, Stephane Gasparini wrote:
> The MSRs will not wrap that often.
Unless some yahoo goes and does WRMSR APERF <big_value_close_to_wrap_around>.
I think we should handle that gracefully too, regardless of how "smart"
that move might be.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-04-01 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6e0c25e64e0fb65a42dfc63ad5f660302e07cd87.1459485198.git.len.brown@intel.com>
2016-04-01 4:37 ` [PATCH] x86: Calculate MHz using APERF/MPERF for cpuinfo and scaling_cur_freq Len Brown
2016-04-01 7:56 ` [PATCH] x86: Calculate MHz using APERF/MPERF for cpuinfo and scaling_cur_freqy Thomas Gleixner
2016-04-01 8:03 ` [PATCH] x86: Calculate MHz using APERF/MPERF for cpuinfo and scaling_cur_freq Peter Zijlstra
2016-04-01 8:16 ` Stephane Gasparini
2016-04-01 8:23 ` Peter Zijlstra
2016-04-01 8:29 ` Peter Zijlstra
2016-04-01 9:30 ` Stephane Gasparini
2016-04-01 9:38 ` Peter Zijlstra
2016-04-01 9:50 ` Borislav Petkov [this message]
2016-04-02 5:22 ` Len Brown
2016-04-01 8:16 ` Peter Zijlstra
2016-04-24 16:38 ` Pavel Machek
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=20160401095005.GA25313@pd.tnic \
--to=bp@alien8.de \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stephane.gasparini@linux.intel.com \
--cc=x86@kernel.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).