From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@linaro.org>,
Chun-Tse Shao <ctshao@google.com>,
Thomas Falcon <thomas.falcon@intel.com>,
Yang Li <yang.lee@linux.alibaba.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/4] Test fixes and debug logging
Date: Fri, 19 Sep 2025 17:46:02 -0300 [thread overview]
Message-ID: <aM3BCr9DbBxnL5rV@x1> (raw)
In-Reply-To: <20250914182900.1960567-1-irogers@google.com>
On Sun, Sep 14, 2025 at 11:28:56AM -0700, Ian Rogers wrote:
> Testing in a hypervisor guest showed some issues that these patches
> try to address, or improve the debug situation upon.
>
> Ian Rogers (4):
> perf test: Be tolerant of missing json metric none value
> perf parse-events: Add debug logging to perf_event
> perf test: Don't fail if user rdpmc returns 0 when disabled
> perf stat-shadow: Display metric-only for 0 counters
Thanks, applied to perf-tools-next,
- Arnaldo
next prev parent reply other threads:[~2025-09-19 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 18:28 [PATCH v1 0/4] Test fixes and debug logging Ian Rogers
2025-09-14 18:28 ` [PATCH v1 1/4] perf test: Be tolerant of missing json metric none value Ian Rogers
2025-09-14 18:28 ` [PATCH v1 2/4] perf parse-events: Add debug logging to perf_event Ian Rogers
2025-09-14 18:28 ` [PATCH v1 3/4] perf test: Don't fail if user rdpmc returns 0 when disabled Ian Rogers
2025-09-14 18:29 ` [PATCH v1 4/4] perf stat-shadow: Display metric-only for 0 counters Ian Rogers
2025-09-19 20:45 ` [PATCH v1 0/4] Test fixes and debug logging Arnaldo Carvalho de Melo
2025-09-19 20:46 ` Arnaldo Carvalho de Melo [this message]
2025-09-20 15:21 ` Ian Rogers
2025-09-24 9:57 ` Arnaldo Carvalho de Melo
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=aM3BCr9DbBxnL5rV@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ctshao@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--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=thomas.falcon@intel.com \
--cc=yang.lee@linux.alibaba.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.