From: Thomas Gleixner <tglx@linutronix.de>
To: Kan Liang <kan.liang@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
acme@kernel.org, eranian@google.com, ak@linux.intel.com
Subject: Re: [PATCH V2 4/4] perf/x86/intel/uncore: SKX support for IIO freerunning counter
Date: Fri, 20 Oct 2017 16:15:44 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1710201327190.1765@nanos> (raw)
In-Reply-To: <1508432137-3984-4-git-send-email-kan.liang@intel.com>
On Thu, 19 Oct 2017, kan.liang@intel.com wrote:
> As of Skylake Server, there are a number of free-running counters in
> each IIO Box that collect counts for per box IO clocks and per Port
> Input/Output x BW/Utilization.
>
> Freerunning counters cannot be written by SW. Counting will be suspended
> only when the IIO Box is powered down.
Free running counters are read only and always active when the IIO box is
powered up.
>
> The bit width of freerunning counter is 36-bit.
Please use 'free running' consistently all over the place.
Thanks,
tglx
next prev parent reply other threads:[~2017-10-20 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 16:55 [PATCH V2 1/4] perf/x86/intel/uncore: use same idx for clinet IMC uncore events kan.liang
2017-10-19 16:55 ` [PATCH V2 2/4] perf/x86/intel/uncore: inline function to check the fixed counter event kan.liang
2017-10-20 14:13 ` Thomas Gleixner
2017-10-19 16:55 ` [PATCH V2 3/4] perf/x86/intel/uncore: add infrastructure for freerunning counters kan.liang
2017-10-20 14:15 ` Thomas Gleixner
2017-10-19 16:55 ` [PATCH V2 4/4] perf/x86/intel/uncore: SKX support for IIO freerunning counter kan.liang
2017-10-20 14:15 ` Thomas Gleixner [this message]
2017-10-20 14:12 ` [PATCH V2 1/4] perf/x86/intel/uncore: use same idx for clinet IMC uncore events Thomas Gleixner
2017-10-20 15:04 ` Liang, Kan
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.20.1710201327190.1765@nanos \
--to=tglx@linutronix.de \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®