From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Jia He <hejianet@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] About pmu cycle counter usage in armv8
Date: Mon, 11 Dec 2017 11:29:31 +0530 [thread overview]
Message-ID: <20171211055930.GA15672@jerin> (raw)
In-Reply-To: <676baa87-777b-ca6e-41c9-7233f90740b6@gmail.com>
-----Original Message-----
> Date: Mon, 11 Dec 2017 13:38:25 +0800
> From: Jia He <hejianet@gmail.com>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>, "dev@dpdk.org"
> <dev@dpdk.org>
> Subject: About pmu cycle counter usage in armv8
> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
> Thunderbird/52.5.0
>
> Hi Jerin
>
> In [1], I met a pmu cycle counter problem (all return value is 0)
> occasionally.
>
> And then I submited a patch to kernel maillist, but was rejected by
> maintainer at last [2].
>
> He said:
>
> "We only intend for the in-kernel perf infrastructure to access
>
> pmccntr_el0; nothing else should touch it."
Yes. That's the reason why
1) A warning added in documentation.
http://dpdk.org/doc/guides/prog_guide/profile_app.html
See at last
"
The PMU based scheme is useful for high accuracy performance profiling
with rte_rdtsc(). However, this method can not be used in conjunction
with Linux userspace profiling tools like perf as this scheme alters the
PMU registers state.
"
2) By default it is disabled and not need for production systems.
Needed only for performance debugging.
>
> So maybe it is not proper for dpdk to use pmu cycle counter?
But, There is no alternative in arm64 to get high resolution counter in
user space(in performance effective way)
>
> [1] http://dpdk.org/ml/archives/dev/2017-November/080998.html
>
> [2]https://lkml.org/lkml/2017/11/16/22
>
> --
> Cheers,
> Jia
>
next prev parent reply other threads:[~2017-12-11 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 5:38 Jia He
2017-12-11 5:59 ` Jerin Jacob [this message]
2017-12-11 6:23 ` Jia He
2017-12-11 6:32 ` Jerin Jacob
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=20171211055930.GA15672@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=hejianet@gmail.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;
as well as URLs for NNTP newsgroup(s).