From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Yang Jihong <yangjihong@bytedance.com>,
peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, james.clark@arm.com,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] perf sched timehist: Add --show-prio & --prio option
Date: Tue, 3 Sep 2024 15:46:23 -0300 [thread overview]
Message-ID: <ZtdZfxSx09lF5MyG@x1> (raw)
In-Reply-To: <CAM9d7cjAVXAqDrT72vjpZvfccaGAZnw_jie5Qz5yX5vSfVWRMw@mail.gmail.com>
On Mon, Aug 19, 2024 at 01:13:43PM -0700, Namhyung Kim wrote:
> On Sun, Aug 18, 2024 at 8:30 PM Yang Jihong <yangjihong@bytedance.com> wrote:
> >
> > This patch set adds --show-prio and --prio to show and filter task priorities.
> > Sometimes may only be interested in the scheduling of certain tasks
> > (such as RT tasks). Support for analyzing events of tasks with given priority(ies)
> > only.
> >
> > Both options are disabled by default, consistent with the original behavior.
> >
> > Changes since v1:
> > - Rebase based on the latest perf-tools-next branch.
> > - Enhance documentation's --prio entry, add a description of how to use multiple priorities. (suggested-by Namhyung)
> >
> > Yang Jihong (2):
> > perf sched timehist: Add --show-prio option
> > perf sched timehist: Add --prio option
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks, applied to perf-tools-next,
- Arnaldo
prev parent reply other threads:[~2024-09-03 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 3:30 [PATCH v2 0/2] perf sched timehist: Add --show-prio & --prio option Yang Jihong
2024-08-19 3:30 ` [PATCH v2 1/2] perf sched timehist: Add --show-prio option Yang Jihong
2024-08-19 3:30 ` [PATCH v2 2/2] perf sched timehist: Add --prio option Yang Jihong
2024-08-19 20:13 ` [PATCH v2 0/2] perf sched timehist: Add --show-prio & " Namhyung Kim
2024-09-03 18:46 ` 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=ZtdZfxSx09lF5MyG@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--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=yangjihong@bytedance.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.