From: Leo Yan <leo.yan@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Namhyung Kim" <namhyung@kernel.org>,
"James Clark" <james.clark@arm.com>,
"Adrián Herrera Arcila" <adrian.herrera@arm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
songliubraving@fb.com, peterz@infradead.org, mingo@redhat.com,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org
Subject: Re: [PATCH 2/2] perf stat: fix unexpected delay behaviour
Date: Thu, 15 Dec 2022 09:45:59 +0800 [thread overview]
Message-ID: <Y5p8V1jkuE6MguRM@leoy-yangtze.lan> (raw)
In-Reply-To: <Y5oJRXnlRju3gDxl@kernel.org>
On Wed, Dec 14, 2022 at 02:35:01PM -0300, Arnaldo Carvalho de Melo wrote:
[...]
> > I don't know anything for eBPF counter, so this is why I am still a bit
> > puzzle which way is right to do (bind vs separate eBPF counters). But
> > I personally prefer to let eBPF counter to respect delay, so it's fine
> > for me to apply Namhyung's patch.
>
> "I'm fine" can be read as an Acked-by, right? :-)
Yes, have sent my Reviewed tag on Namhyung's patch.
Thanks,
Leo
next prev parent reply other threads:[~2022-12-15 1:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 16:12 [PATCH 1/2] perf stat: refactor __run_perf_stat common code Adrián Herrera Arcila
2022-07-29 16:12 ` [PATCH 2/2] perf stat: fix unexpected delay behaviour Adrián Herrera Arcila
2022-08-01 8:20 ` James Clark
2022-12-13 14:44 ` Arnaldo Carvalho de Melo
2022-12-13 16:40 ` Namhyung Kim
2022-12-14 14:26 ` James Clark
2022-12-14 14:41 ` Arnaldo Carvalho de Melo
2022-12-14 15:57 ` Leo Yan
2022-12-14 17:35 ` Arnaldo Carvalho de Melo
2022-12-15 1:45 ` Leo Yan [this message]
2022-08-01 11:45 ` Leo Yan
2022-08-01 11:27 ` [PATCH 1/2] perf stat: refactor __run_perf_stat common code Leo Yan
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=Y5p8V1jkuE6MguRM@leoy-yangtze.lan \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=adrian.herrera@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=songliubraving@fb.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®