From: Leo Yan <leo.yan@linaro.org>
To: Denis Nikitin <denik@google.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Mike Leach <mike.leach@linaro.org>,
"coresight@lists.linaro.org" <coresight@lists.linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Daniel Kiss <Daniel.Kiss@arm.com>
Subject: Re: [PATCH 0/4] coresight: Add ETR-PERF polling.
Date: Tue, 18 May 2021 22:14:10 +0800 [thread overview]
Message-ID: <20210518141410.GD942578@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20210518140040.GC942578@leoy-ThinkPad-X240s>
On Tue, May 18, 2021 at 10:00:40PM +0800, Leo Yan wrote:
[...]
> > We could probably utilize the ETM strobing feature and reduce frequency
> > of data collection but I see a problem when I'm using both.
> > Within a minute of profiling the ETM generates a reasonable profile size
> > (with strobing autofdo,preset=9 with period 0x1000 it is up to 20MB).
> > But then the size grows unproportionally.
> > With a 4 minute run I got a 6.3GB profile.
> >
> > I don't see such a problem with the ETR polling patch.
> >
> > Leo, could you please take a look at this problem?
Or in the other way, could you share the perf data files?
Base on the perf data files, I think at least we can confirm what's the
AUX trace data size for every period, and we might also can quickly
confirm if the strobing configurations are lost or not in the middle of
tracing (To be honest, I have no knowledge for strobing, so need Mike's
help for confirmation).
Thanks,
Leo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-18 14:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 12:04 [PATCH 0/4] coresight: Add ETR-PERF polling Daniel Kiss
2021-04-21 12:04 ` [PATCH 1/4] coresight: tmc-etr: Advance buffer pointer in sync buffer Daniel Kiss
2021-04-23 8:23 ` Leo Yan
2021-04-26 10:40 ` Suzuki K Poulose
2021-04-27 3:45 ` Leo Yan
2021-04-27 10:00 ` Suzuki K Poulose
2021-04-28 2:34 ` Leo Yan
2021-04-21 12:04 ` [PATCH 2/4] coresight: tmc-etr: Track perf handler Daniel Kiss
2021-04-23 9:20 ` Leo Yan
2021-04-26 0:25 ` Leo Yan
2021-04-21 12:04 ` [PATCH 3/4] coresight: etm-perf: Export etm_event_cpu_path Daniel Kiss
2021-04-21 12:04 ` [PATCH 4/4] coresight: Add ETR-PERF polling Daniel Kiss
2021-04-26 1:18 ` Leo Yan
2021-05-05 7:21 ` Denis Nikitin
2021-04-26 17:54 ` [PATCH 0/4] " Mathieu Poirier
2021-04-27 10:43 ` Al Grant
2021-04-27 14:41 ` Mike Leach
2021-04-27 15:47 ` Mathieu Poirier
2021-04-27 16:04 ` Leo Yan
2021-05-05 6:46 ` Denis Nikitin
2021-05-05 15:29 ` Mathieu Poirier
2021-05-14 9:02 ` Denis Nikitin
2021-05-14 16:16 ` Mike Leach
2021-05-18 14:00 ` Leo Yan
2021-05-18 14:14 ` Leo Yan [this message]
2021-05-18 15:41 ` Mathieu Poirier
2021-05-26 6:47 ` Denis Nikitin
2021-05-23 8:45 ` Leo Yan
2021-05-27 7:50 ` Denis Nikitin
2021-05-27 15:07 ` Leo Yan
2021-05-27 16:22 ` Denis Nikitin
2021-05-28 16:37 ` Leo Yan
2021-04-27 16:24 ` James Clark
2021-04-28 11:30 ` James Clark
2021-04-28 11:52 ` Daniel Kiss
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=20210518141410.GD942578@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=Daniel.Kiss@arm.com \
--cc=coresight@lists.linaro.org \
--cc=denik@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.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 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.