From: Petar Gligoric <petar.gligor@gmail.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Petar Gligoric <petar.gligoric@rohde-schwarz.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Andi Kleen <ak@linux.intel.com>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Hagen Paul Pfeifer <hagen@jauu.net>
Subject: Re: [PATCH v2 0/3] perf: introduce perf based task analyzer
Date: Thu, 8 Dec 2022 15:11:41 -0500 [thread overview]
Message-ID: <Y5JE/ci+1nN9RrJQ@debian> (raw)
In-Reply-To: <CAM9d7ciX9ULwSy5G3cFZi7mMXrt_A52hwwk7L1m-oV_0P07_vw@mail.gmail.com>
>On Thu, Dec 08, 2022 at 11:10:58AM -0800, Namhyung Kim wrote:
>
> Then I have no problem with python. Please take a look at the
> scripts/python/bin directory to provide shortcuts for record/report.
>
> Thanks,
> Namhyung
>
>
Great that we could resolve it! Regarding wrapper: I thought I added
them or did you mean something else?
.../scripts/python/bin/tasks-analyzer-record | 2 +
.../scripts/python/bin/tasks-analyzer-report | 3 +
Best Regards,
Petar
next prev parent reply other threads:[~2022-12-08 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 15:44 [PATCH v2 0/3] perf: introduce perf based task analyzer Petar Gligoric
2022-12-06 15:44 ` [PATCH v2 1/3] perf script: introduce " Petar Gligoric
2022-12-06 15:44 ` [PATCH v2 2/3] perf script: task-analyzer add csv support Petar Gligoric
2022-12-06 15:44 ` [PATCH v2 3/3] perf test: add new task-analyzer tests Petar Gligoric
2022-12-06 18:32 ` [PATCH v2 0/3] perf: introduce perf based task analyzer Namhyung Kim
2022-12-06 22:21 ` Petar Gligoric
2022-12-08 4:59 ` Namhyung Kim
2022-12-08 12:15 ` Petar Gligoric
2022-12-08 19:10 ` Namhyung Kim
2022-12-08 20:11 ` Petar Gligoric [this message]
2022-12-08 20:15 ` Namhyung Kim
2022-12-12 20:03 ` 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=Y5JE/ci+1nN9RrJQ@debian \
--to=petar.gligor@gmail.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=hagen@jauu.net \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=petar.gligoric@rohde-schwarz.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