From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Jan Viktorin <viktorin@rehivetech.com>
Cc: Nipun Gupta <nipun.gupta@nxp.com>,
dev@dpdk.org, "jianbo.liu@linaro.org" <jianbo.liu@linaro.org>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [PATCH] eal/armv8: high-resolution cycle counter
Date: Tue, 04 Oct 2016 10:42:49 +0200 [thread overview]
Message-ID: <5251875.5YmvKy6xFj@xps13> (raw)
In-Reply-To: <20160819125217.GA7169@localhost.localdomain>
2016-08-19 18:22, Jerin Jacob:
> On Fri, Aug 19, 2016 at 02:24:58PM +0200, Jan Viktorin wrote:
> > On Fri, 19 Aug 2016 17:16:12 +0530
> > Jerin Jacob <jerin.jacob@caviumnetworks.com> wrote:
> >
> >
> > I've got a private kernel driver enabling and disabling (hopefully) properly
> > this for ARMv7. If we'd like to merge it, I'd like to have a single module
> > or at least single module with 2 implementations...
> >
> > I can post it if it would be helpful.
>
> I don't think we can use this in production as this may alter PMU state used
> by 'perf' etc.I think let it be a debug interface for armv7 and armv8
> and disable it by default.
Please could you document the use of PMU for debug and how it alters
usage of kernel counters?
A patch in doc/guides/prog_guide/profile_app.rst would be welcome.
Ideally, it would be a lot better to have a sysfs entry to enable PMU
counter with an upstream kernel.
next prev parent reply other threads:[~2016-10-04 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 11:51 [PATCH] eal/armv8: high-resolution cycle counter Jerin Jacob
2016-08-19 9:43 ` Nipun Gupta
2016-08-19 11:46 ` Jerin Jacob
2016-08-19 12:24 ` Jan Viktorin
2016-08-19 12:52 ` Jerin Jacob
2016-10-04 8:42 ` Thomas Monjalon [this message]
2016-08-23 10:01 ` Hemant Agrawal
2016-10-04 8:46 ` Thomas Monjalon
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=5251875.5YmvKy6xFj@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@linaro.org \
--cc=nipun.gupta@nxp.com \
--cc=viktorin@rehivetech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.