From: Mark Rutland <mark.rutland@arm.com>
To: Zhengyu Shen <zhengyu.shen@nxp.com>
Cc: "shawnguo@kernel.org" <shawnguo@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
Frank Li <frank.li@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"acme@kernel.org" <acme@kernel.org>,
"alexander.shishkin@linux.intel.com"
<alexander.shishkin@linux.intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"lznuaa@gmail.com" <lznuaa@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] Added perf functionality to mmdc driver
Date: Wed, 17 Aug 2016 11:04:25 +0100 [thread overview]
Message-ID: <20160817100425.GB30900@leverpostej> (raw)
In-Reply-To: <DB5PR04MB1430F6105A94E0E95FF3C8FF9F130@DB5PR04MB1430.eurprd04.prod.outlook.com>
On Tue, Aug 16, 2016 at 08:40:08PM +0000, Zhengyu Shen wrote:
> > > > > + hrtimer_start(&pmu_mmdc->hrtimer, mmdc_timer_period(),
> > > > > + HRTIMER_MODE_REL_PINNED);
> > > >
> > > > Why is a hrtimer necessary? Is this just copy-pasted from CCN, or do
> > > > you have similar HW issues?
> > > >
> > > > Is there no overflow interrupt?
> > >
> > > When overflow occurs, a register bit is set to one. There is no
> > > overflow interrupt which is why the timer is needed.
> >
> > I see. Please have add comment in the driver explaining this, so that this is
> > obvious.
> >
> > Does the counter itself wrap and continue counting, or does it saturate?
> >
> > How have you tuned your polling period so as to avoid missing events in the
> > case of an overflow?
> >
> > Thanks,
> > Mark.
> The counter wraps around once every ten seconds for total-cycles (which is the
> Fastest increasing counter). Polling is done every one second just to be safe.
Ok. It would be worth noting this with a comment next to either the
hrtimer handler or registration thereof.
I assume that on overflow the counter wraps rather than saturating?
Thanks,
Mark.
next prev parent reply other threads:[~2016-08-17 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 22:30 Zhengyu Shen
2016-08-15 16:50 ` Mark Rutland
2016-08-16 12:04 ` Peter Zijlstra
2016-08-16 14:40 ` Zhengyu Shen
2016-08-15 19:49 ` Mark Rutland
2016-08-16 20:40 ` Zhengyu Shen
2016-08-17 10:04 ` Mark Rutland [this message]
2016-08-16 0:25 ` kbuild test robot
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=20160817100425.GB30900@leverpostej \
--to=mark.rutland@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=frank.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shawnguo@kernel.org \
--cc=zhengyu.shen@nxp.com \
/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®