All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: German Gomez <german.gomez@arm.com>
Cc: Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Leo Yan <leo.yan@linaro.org>, Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH v1 2/4] perf script: Add "struct machine" parameter to process_event callback
Date: Mon, 13 Dec 2021 15:22:52 -0300	[thread overview]
Message-ID: <YbePfOMaiJjoDb3b@kernel.org> (raw)
In-Reply-To: <38fd4992-63ae-4871-ddfd-27d40b5c48d2@arm.com>

Em Fri, Dec 03, 2021 at 12:00:26PM +0000, German Gomez escreveu:
> Hi Athira,
> 
> On 02/12/2021 16:03, Athira Rajeev wrote:
> >
> >> On 01-Dec-2021, at 6:03 PM, German Gomez <german.gomez@arm.com> wrote:
> >>
> >> Include a "struct machine*" parameter to the process_event callback in
> >> the scripting layer. This will allow access to the perf_env from within
> >> this callback.
> >>
> >> Followup patches will build on top of this to report the correct name of
> >> the registers in a perf.data file, consistently with the architecture
> >> the file was recorded in.
> >>
> >> Signed-off-by: German Gomez <german.gomez@arm.com>
> >> ---
> >> tools/perf/builtin-script.c                   |  2 +-
> >> .../util/scripting-engines/trace-event-perl.c |  3 ++-
> >> .../scripting-engines/trace-event-python.c    | 23 +++++++++++--------
> >> tools/perf/util/trace-event-scripting.c       |  3 ++-
> >> tools/perf/util/trace-event.h                 |  3 ++-
> >> 5 files changed, 21 insertions(+), 13 deletions(-)
> >>
> >> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> >> index 9434367af..711132f0b 100644
> >> --- a/tools/perf/builtin-script.c
> >> +++ b/tools/perf/builtin-script.c
> >> @@ -2256,7 +2256,7 @@ static int process_sample_event(struct perf_tool *tool,
> >> 				thread__resolve(al.thread, &addr_al, sample);
> >> 			addr_al_ptr = &addr_al;
> >> 		}
> >> -		scripting_ops->process_event(event, sample, evsel, &al, addr_al_ptr);
> >> +		scripting_ops->process_event(event, sample, evsel, &al, addr_al_ptr, machine);
> > Hi,
> >
> > Looks like the patch is using “machine” to allow access to perf_env__arch and there by to get the “arch” value.
> > But can we use from evsel, like  "perf_env__arch(evsel__env(evsel))” to get arch value instead of including new parameter for “struct machine” ?
> >
> > Thanks
> > Athira
> 
> Thanks for the suggestion. It looks like we can skip this patch if we
> can get the arch value that way.

So the first one is already upstream, will you post a v2?

- Arnaldo

WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: German Gomez <german.gomez@arm.com>
Cc: Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Leo Yan <leo.yan@linaro.org>, Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH v1 2/4] perf script: Add "struct machine" parameter to process_event callback
Date: Mon, 13 Dec 2021 15:22:52 -0300	[thread overview]
Message-ID: <YbePfOMaiJjoDb3b@kernel.org> (raw)
In-Reply-To: <38fd4992-63ae-4871-ddfd-27d40b5c48d2@arm.com>

Em Fri, Dec 03, 2021 at 12:00:26PM +0000, German Gomez escreveu:
> Hi Athira,
> 
> On 02/12/2021 16:03, Athira Rajeev wrote:
> >
> >> On 01-Dec-2021, at 6:03 PM, German Gomez <german.gomez@arm.com> wrote:
> >>
> >> Include a "struct machine*" parameter to the process_event callback in
> >> the scripting layer. This will allow access to the perf_env from within
> >> this callback.
> >>
> >> Followup patches will build on top of this to report the correct name of
> >> the registers in a perf.data file, consistently with the architecture
> >> the file was recorded in.
> >>
> >> Signed-off-by: German Gomez <german.gomez@arm.com>
> >> ---
> >> tools/perf/builtin-script.c                   |  2 +-
> >> .../util/scripting-engines/trace-event-perl.c |  3 ++-
> >> .../scripting-engines/trace-event-python.c    | 23 +++++++++++--------
> >> tools/perf/util/trace-event-scripting.c       |  3 ++-
> >> tools/perf/util/trace-event.h                 |  3 ++-
> >> 5 files changed, 21 insertions(+), 13 deletions(-)
> >>
> >> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> >> index 9434367af..711132f0b 100644
> >> --- a/tools/perf/builtin-script.c
> >> +++ b/tools/perf/builtin-script.c
> >> @@ -2256,7 +2256,7 @@ static int process_sample_event(struct perf_tool *tool,
> >> 				thread__resolve(al.thread, &addr_al, sample);
> >> 			addr_al_ptr = &addr_al;
> >> 		}
> >> -		scripting_ops->process_event(event, sample, evsel, &al, addr_al_ptr);
> >> +		scripting_ops->process_event(event, sample, evsel, &al, addr_al_ptr, machine);
> > Hi,
> >
> > Looks like the patch is using “machine” to allow access to perf_env__arch and there by to get the “arch” value.
> > But can we use from evsel, like  "perf_env__arch(evsel__env(evsel))” to get arch value instead of including new parameter for “struct machine” ?
> >
> > Thanks
> > Athira
> 
> Thanks for the suggestion. It looks like we can skip this patch if we
> can get the arch value that way.

So the first one is already upstream, will you post a v2?

- Arnaldo

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: German Gomez <german.gomez@arm.com>
Cc: Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	John Garry <john.garry@huawei.com>, Will Deacon <will@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Leo Yan <leo.yan@linaro.org>, Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH v1 2/4] perf script: Add "struct machine" parameter to process_event callback
Date: Mon, 13 Dec 2021 15:22:52 -0300	[thread overview]
Message-ID: <YbePfOMaiJjoDb3b@kernel.org> (raw)
In-Reply-To: <38fd4992-63ae-4871-ddfd-27d40b5c48d2@arm.com>

Em Fri, Dec 03, 2021 at 12:00:26PM +0000, German Gomez escreveu:
> Hi Athira,
> 
> On 02/12/2021 16:03, Athira Rajeev wrote:
> >
> >> On 01-Dec-2021, at 6:03 PM, German Gomez <german.gomez@arm.com> wrote:
> >>
> >> Include a "struct machine*" parameter to the process_event callback in
> >> the scripting layer. This will allow access to the perf_env from within
> >> this callback.
> >>
> >> Followup patches will build on top of this to report the correct name of
> >> the registers in a perf.data file, consistently with the architecture
> >> the file was recorded in.
> >>
> >> Signed-off-by: German Gomez <german.gomez@arm.com>
> >> ---
> >> tools/perf/builtin-script.c                   |  2 +-
> >> .../util/scripting-engines/trace-event-perl.c |  3 ++-
> >> .../scripting-engines/trace-event-python.c    | 23 +++++++++++--------
> >> tools/perf/util/trace-event-scripting.c       |  3 ++-
> >> tools/perf/util/trace-event.h                 |  3 ++-
> >> 5 files changed, 21 insertions(+), 13 deletions(-)
> >>
> >> diff --git a/tools/perf/builtin-script.c b/tools/perf/builtin-script.c
> >> index 9434367af..711132f0b 100644
> >> --- a/tools/perf/builtin-script.c
> >> +++ b/tools/perf/builtin-script.c
> >> @@ -2256,7 +2256,7 @@ static int process_sample_event(struct perf_tool *tool,
> >> 				thread__resolve(al.thread, &addr_al, sample);
> >> 			addr_al_ptr = &addr_al;
> >> 		}
> >> -		scripting_ops->process_event(event, sample, evsel, &al, addr_al_ptr);
> >> +		scripting_ops->process_event(event, sample, evsel, &al, addr_al_ptr, machine);
> > Hi,
> >
> > Looks like the patch is using “machine” to allow access to perf_env__arch and there by to get the “arch” value.
> > But can we use from evsel, like  "perf_env__arch(evsel__env(evsel))” to get arch value instead of including new parameter for “struct machine” ?
> >
> > Thanks
> > Athira
> 
> Thanks for the suggestion. It looks like we can skip this patch if we
> can get the arch value that way.

So the first one is already upstream, will you post a v2?

- Arnaldo

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-12-13 18:22 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 12:33 [PATCH v1 0/4] Support register names from all architectures German Gomez
2021-12-01 12:33 ` German Gomez
2021-12-01 12:33 ` German Gomez
2021-12-01 12:33 ` [PATCH v1 1/4] perf tools: Prevent out-of-bounds access to registers German Gomez
2021-12-01 12:33   ` German Gomez
2021-12-01 12:33   ` German Gomez
2021-12-08 21:35   ` Jiri Olsa
2021-12-08 21:35     ` Jiri Olsa
2021-12-08 21:35     ` Jiri Olsa
2021-12-10  9:17   ` kajoljain
2021-12-10  9:17     ` kajoljain
2021-12-10  9:17     ` kajoljain
2021-12-10 13:38     ` Arnaldo Carvalho de Melo
2021-12-10 13:38       ` Arnaldo Carvalho de Melo
2021-12-10 13:38       ` Arnaldo Carvalho de Melo
2021-12-10 15:28       ` German Gomez
2021-12-10 15:28         ` German Gomez
2021-12-10 15:28         ` German Gomez
2021-12-10 16:19         ` Arnaldo Carvalho de Melo
2021-12-10 16:19           ` Arnaldo Carvalho de Melo
2021-12-10 16:19           ` Arnaldo Carvalho de Melo
2021-12-01 12:33 ` [PATCH v1 2/4] perf script: Add "struct machine" parameter to process_event callback German Gomez
2021-12-01 12:33   ` German Gomez
2021-12-01 12:33   ` German Gomez
2021-12-02 16:03   ` Athira Rajeev
2021-12-02 16:03     ` Athira Rajeev
2021-12-02 16:03     ` Athira Rajeev
2021-12-03 12:00     ` German Gomez
2021-12-03 12:00       ` German Gomez
2021-12-03 12:00       ` German Gomez
2021-12-13 18:22       ` Arnaldo Carvalho de Melo [this message]
2021-12-13 18:22         ` Arnaldo Carvalho de Melo
2021-12-13 18:22         ` Arnaldo Carvalho de Melo
2021-12-13 18:31         ` German Gomez
2021-12-13 18:31           ` German Gomez
2021-12-13 18:31           ` German Gomez
2021-12-13 19:59           ` Arnaldo Carvalho de Melo
2021-12-13 19:59             ` Arnaldo Carvalho de Melo
2021-12-13 19:59             ` Arnaldo Carvalho de Melo
2021-12-01 12:33 ` [PATCH v1 3/4] perf tools: Crete header files with register names German Gomez
2021-12-01 12:33   ` German Gomez
2021-12-01 12:33   ` German Gomez
2021-12-01 12:33 ` [PATCH v1 4/4] perf tools: Support register names from all architectures German Gomez
2021-12-01 12:33   ` German Gomez
2021-12-01 12:33   ` German Gomez
2021-12-03  9:38   ` German Gomez
2021-12-03  9:38     ` German Gomez
2021-12-03  9:38     ` German Gomez

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=YbePfOMaiJjoDb3b@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=german.gomez@arm.com \
    --cc=john.garry@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-csky@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=namhyung@kernel.org \
    --cc=will@kernel.org \
    /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.