public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Ian Rogers <irogers@google.com>,
	Dima Kogan <dima@secretsauce.net>,
	Alexander Lobakin <aleksander.lobakin@intel.com>,
	Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] perf-probe: Improbe non-C language support
Date: Tue, 10 Dec 2024 15:40:59 -0300	[thread overview]
Message-ID: <Z1iLO-JHiVj_c1Vp@x1> (raw)
In-Reply-To: <173145727287.2747044.14103970580490941023.stgit@mhiramat.roam.corp.google.com>

On Wed, Nov 13, 2024 at 09:21:13AM +0900, Masami Hiramatsu (Google) wrote:
> Hi,
> 
> Here is the 3rd version of patches for perf probe to improve non-C language
> (e.g. Rust, Go) support.
> 
> This ported the last patch on top of tmp.perf-tools-next, and add a fix patch
> for compilation errors.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git tmp.perf-tools-next
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git/log/?h=tmp.perf-tools-next


Thanks, applied the first patch to perf-tools-next, the other was folded
into the patch that introduced those problems, to avoid bisection
problems.

- Arnaldo
 
> Thank you,
> 
> ---
> 
> Masami Hiramatsu (Google) (2):
>       perf-probe: Replace unacceptable characters when generating event name
>       perf disasm: Fix compilation error with stubs
> 
> 
>  tools/perf/util/disasm.c       |    7 ++++---
>  tools/perf/util/probe-event.c  |   32 +++++++++++++++++++++++++-------
>  tools/perf/util/probe-event.h  |    3 ++-
>  tools/perf/util/probe-finder.c |   15 +++++++++++++++
>  tools/perf/util/probe-finder.h |    5 +++++
>  5 files changed, 51 insertions(+), 11 deletions(-)
> 
> --
> Masami Hiramatsu (Google) <mhiramat@kernel.org>

      parent reply	other threads:[~2024-12-10 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13  0:21 [PATCH v3 0/2] perf-probe: Improbe non-C language support Masami Hiramatsu (Google)
2024-11-13  0:21 ` [PATCH v3 1/2] perf-probe: Replace unacceptable characters when generating event name Masami Hiramatsu (Google)
2024-11-13  0:21 ` [PATCH v3 2/2] perf disasm: Fix compilation error with stubs Masami Hiramatsu (Google)
2024-12-10 18:40 ` 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=Z1iLO-JHiVj_c1Vp@x1 \
    --to=acme@kernel.org \
    --cc=aleksander.lobakin@intel.com \
    --cc=dima@secretsauce.net \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=przemyslaw.kitszel@intel.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