The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	james.clark@linaro.org, howardchu95@gmail.com, neelx@suse.com,
	chjohnst@mail.com, sean@ashe.io, steve@abita.co,
	rishil1999@outlook.com, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/4] perf sched latency: Refine outputs, unit scaling, and histogram support
Date: Wed, 5 Aug 2026 22:04:25 -0700	[thread overview]
Message-ID: <anQV2fx7jhSzql_D@google.com> (raw)
In-Reply-To: <20260805210751.287746-1-atomlin@atomlin.com>

Hello,

On Wed, Aug 05, 2026 at 05:07:47PM -0400, Aaron Tomlin wrote:
> Hi Namhyung, Ian, Arnaldo,
> 
> This patch series improves 'perf sched latency' by suppressing misleading
> empty table output, extending pipe mode stream processing, introducing
> dynamic unit auto-scaling for latency and runtime statistics, and adding
> latency histogram visualisation alongside time-span filtering.

Thanks for working on this.  But it doesn't apply unfortunately.
Can you please rebase on to the current perf-tools-next?

Thanks,
Namhyung

      parent reply	other threads:[~2026-08-06  5:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 21:07 [PATCH v8 0/4] perf sched latency: Refine outputs, unit scaling, and histogram support Aaron Tomlin
2026-08-05 21:07 ` [PATCH v8 1/4] perf sched: Suppress latency table output when trace samples are missing Aaron Tomlin
2026-08-05 21:07 ` [PATCH v8 2/4] perf sched: Handle missing trace samples in pipe mode Aaron Tomlin
2026-08-05 21:07 ` [PATCH v8 3/4] perf sched latency: Auto-scale latency and runtime display units Aaron Tomlin
2026-08-05 21:07 ` [PATCH v8 4/4] perf sched latency: Add histogram and time interval options Aaron Tomlin
2026-08-05 22:02 ` [PATCH v8 0/4] perf sched latency: Refine outputs, unit scaling, and histogram support Ian Rogers
2026-08-06 14:05   ` Aaron Tomlin
2026-08-06  5:04 ` Namhyung Kim [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=anQV2fx7jhSzql_D@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=atomlin@atomlin.com \
    --cc=chjohnst@mail.com \
    --cc=howardchu95@gmail.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --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=neelx@suse.com \
    --cc=peterz@infradead.org \
    --cc=rishil1999@outlook.com \
    --cc=sean@ashe.io \
    --cc=steve@abita.co \
    /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