LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gautam Menghani <gautam@linux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Tejas Manhas <tejas05@linux.ibm.com>,
	Gautam Menghani <Gautam.Menghani@ibm.com>,
	peterz@infradead.org, mingo@redhat.com, namhyung@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, atrajeev@linux.ibm.com,
	linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf script powerpc: Update the hcall list with new hcalls
Date: Tue, 2 Jun 2026 17:36:31 +0530	[thread overview]
Message-ID: <ah7HRzA8ddE7dY90@mac.bl1-in.ibm.com> (raw)
In-Reply-To: <ahoo5dI-6fVlFvvR@x1>

On Fri, May 29, 2026 at 09:01:41PM -0300, Arnaldo Carvalho de Melo wrote:
> On Wed, May 20, 2026 at 09:25:08AM +0530, Tejas Manhas wrote:
> > From: Gautam Menghani [1]<gautam@linux.ibm.com>
> > 
> > Update the hcall list with the hcalls in bcc's ppchcalls script [1].
> > 
> > [1] : [2]https://github.com/iovisor/bcc/blob/master/tools/ppchcalls.py
> > 
> > 
> > Hi Gautam,
> > 
> > This patch doesn't seem to resolve the issue where numbers are seen instead of h
> > calls.
> > I have applied to the latest upstream but the numbers are still visible in perf
> > script.
> > Also the command doesn't recognise python-audit already present in the system.
> > 
> > Please find logs below for better understanding.
> 
> Any progress on this?

Yeah, sent a v2 - https://lore.kernel.org/all/20260602115644.8133-1-Gautam.Menghani@ibm.com/

Thanks,
Gautam


      reply	other threads:[~2026-06-02 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  8:46 [PATCH] perf script powerpc: Update the hcall list with new hcalls Gautam Menghani
2026-05-20  3:55 ` Tejas Manhas
2026-05-30  0:01   ` Arnaldo Carvalho de Melo
2026-06-02 12:06     ` Gautam Menghani [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=ah7HRzA8ddE7dY90@mac.bl1-in.ibm.com \
    --to=gautam@linux.ibm.com \
    --cc=Gautam.Menghani@ibm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=atrajeev@linux.ibm.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=linuxppc-dev@lists.ozlabs.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tejas05@linux.ibm.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