From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Veronika Molnarova <vmolnaro@redhat.com>
Cc: Ian Rogers <irogers@google.com>,
linux-perf-users@vger.kernel.org, acme@redhat.com,
mpetlan@redhat.com, peterz@infradead.org, mingo@redhat.com,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
adrian.hunter@intel.co, kan.liang@linux.intel.com,
yangyicong@hisilicon.com, tim.c.chen@linux.intel.com
Subject: Re: [PATCH] perf test: Parse perf stat Topdown events for aarch64
Date: Tue, 10 Dec 2024 15:45:34 -0300 [thread overview]
Message-ID: <Z1iMTjb3kXp0TC7u@x1> (raw)
In-Reply-To: <51789413-f4d4-4085-afeb-aedffc36c3c3@redhat.com>
On Tue, Dec 10, 2024 at 04:13:27PM +0100, Veronika Molnarova wrote:
> On 11/18/24 22:31, Ian Rogers wrote:
> > On Mon, Nov 18, 2024 at 2:04 AM Veronika Molnarova <vmolnaro@redhat.com> wrote:
> >> On 10/29/24 16:25, Ian Rogers wrote:
> >>> I saw similar issues and sent:
> >>> https://lore.kernel.org/lkml/20240417183219.1208493-1-irogers@google.com/
> >>> but got distracted. A difference there is automating the generation of
> >>> the skip_metric list rather than hard coding it. Hard coding may be
> >>> the most pragmatic thing to do in the near term.
> >> Automating the skip_metric list generation would be great, but for
> >> the time being, we can stick with hard coding until there is such
> >> possibility.
> > Acked-by: Ian Rogers <irogers@google.com>
> Ping on this patch. Please let me know if it's missing anything.
Thanks, applied to perf-tools-next.
- Arnaldo
prev parent reply other threads:[~2024-12-10 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 14:43 [PATCH] perf test: Parse perf stat Topdown events for aarch64 vmolnaro
2024-10-29 15:25 ` Ian Rogers
2024-11-18 10:04 ` Veronika Molnarova
2024-11-18 21:31 ` Ian Rogers
2024-12-10 15:13 ` Veronika Molnarova
2024-12-10 18:45 ` Arnaldo Carvalho de Melo [this message]
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=Z1iMTjb3kXp0TC7u@x1 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.co \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tim.c.chen@linux.intel.com \
--cc=vmolnaro@redhat.com \
--cc=yangyicong@hisilicon.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.