linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Ian Rogers <irogers@google.com>,
	Namhyung Kim <namhyung@kernel.org>
Cc: linux-perf-users <linux-perf-users@vger.kernel.org>,
	Kajol Jain <kjain@linux.ibm.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	disgoel@linux.vnet.ibm.com
Subject: Re: [PATCH 1/3] tools/perf/arch/powerpc: Add load/store in powerpc annotate instructions for data type profling
Date: Sat, 9 Mar 2024 12:48:46 +0530	[thread overview]
Message-ID: <D1EBC8FF-80A4-4A2A-BEAC-E170EB4400CB@linux.vnet.ibm.com> (raw)
In-Reply-To: <20240309055136.96556-2-atrajeev@linux.vnet.ibm.com>

Hi All,

Please ignore this version. I made mistake in cover letter. I am re-posting the correct version now.
Sorry for the confusion

Thanks
Athira

> On 09-Mar-2024, at 11:21 AM, Athira Rajeev <atrajeev@linux.vnet.ibm.com> wrote:
> 
> Add powerpc instruction nmemonic table to associate load/store
> instructions with move_ops. mov_ops is used to identify mem_type
> to associate instruction with data type and offset. Also initialize
> and allocate arch specific fields for nr_instructions, instructions and
> nr_instructions_allocate.
> 
> Signed-off-by: Athira Rajeev <atrajeev@linux.vnet.ibm.com>
> ---
> .../perf/arch/powerpc/annotate/instructions.c | 66 +++++++++++++++++++
> 1 file changed, 66 insertions(+)
> 
> diff --git a/tools/perf/arch/powerpc/annotate/instructions.c b/tools/perf/arch/powerpc/annotate/instructions.c
> index a3f423c27cae..07af4442be38 100644
> --- a/tools/perf/arch/powerpc/annotate/instructions.c
> +++ b/tools/perf/arch/powerpc/annotate/instructions.c
> @@ -1,6 +1,65 @@
> // SPDX-License-Identifier: GPL-2.0
> #include <linux/compiler.h>
> 
> +/*
> + * powerpc instruction nmemonic table to associate load/store instructions with
> + * move_ops. mov_ops is used to identify mem_type to associate instruction with
> + * data type and offset.
> + */
> +static struct ins powerpc__instructions[] = {
> + { .name = "lbz", .ops = &mov_ops,  },
> + { .name = "lbzx", .ops = &mov_ops,  },
> + { .name = "lbzu", .ops = &mov_ops,  },
> + { .name = "lbzux", .ops = &mov_ops,  },
> + { .name = "lhz", .ops = &mov_ops,  },
> + { .name = "lhzx", .ops = &mov_ops,  },
> + { .name = "lhzu", .ops = &mov_ops,  },
> + { .name = "lhzux", .ops = &mov_ops,  },
> + { .name = "lha", .ops = &mov_ops,  },
> + { .name = "lhax", .ops = &mov_ops,  },
> + { .name = "lhau", .ops = &mov_ops,  },
> + { .name = "lhaux", .ops = &mov_ops,  },
> + { .name = "lwz", .ops = &mov_ops,  },
> + { .name = "lwzx", .ops = &mov_ops,  },
> + { .name = "lwzu", .ops = &mov_ops,  },
> + { .name = "lwzux", .ops = &mov_ops,  },
> + { .name = "lwa", .ops = &mov_ops,  },
> + { .name = "lwax", .ops = &mov_ops,  },
> + { .name = "lwaux", .ops = &mov_ops,  },
> + { .name = "ld", .ops = &mov_ops,  },
> + { .name = "ldx", .ops = &mov_ops,  },
> + { .name = "ldu", .ops = &mov_ops,  },
> + { .name = "ldux", .ops = &mov_ops,  },
> + { .name = "stb", .ops = &mov_ops,  },
> + { .name = "stbx", .ops = &mov_ops,  },
> + { .name = "stbu", .ops = &mov_ops,  },
> + { .name = "stbux", .ops = &mov_ops,  },
> + { .name = "sth", .ops = &mov_ops,  },
> + { .name = "sthx", .ops = &mov_ops,  },
> + { .name = "sthu", .ops = &mov_ops,  },
> + { .name = "sthux", .ops = &mov_ops,  },
> + { .name = "stw", .ops = &mov_ops,  },
> + { .name = "stwx", .ops = &mov_ops,  },
> + { .name = "stwu", .ops = &mov_ops,  },
> + { .name = "stwux", .ops = &mov_ops,  },
> + { .name = "std", .ops = &mov_ops,  },
> + { .name = "stdx", .ops = &mov_ops,  },
> + { .name = "stdu", .ops = &mov_ops,  },
> + { .name = "stdux", .ops = &mov_ops,  },
> + { .name = "lhbrx", .ops = &mov_ops,  },
> + { .name = "sthbrx", .ops = &mov_ops,  },
> + { .name = "lwbrx", .ops = &mov_ops,  },
> + { .name = "stwbrx", .ops = &mov_ops,  },
> + { .name = "ldbrx", .ops = &mov_ops,  },
> + { .name = "stdbrx", .ops = &mov_ops,  },
> + { .name = "lmw", .ops = &mov_ops,  },
> + { .name = "stmw", .ops = &mov_ops,  },
> + { .name = "lswi", .ops = &mov_ops,  },
> + { .name = "lswx", .ops = &mov_ops,  },
> + { .name = "stswi", .ops = &mov_ops,  },
> + { .name = "stswx", .ops = &mov_ops,  },
> +};
> +
> static struct ins_ops *powerpc__associate_instruction_ops(struct arch *arch, const char *name)
> {
> int i;
> @@ -52,6 +111,13 @@ static struct ins_ops *powerpc__associate_instruction_ops(struct arch *arch, con
> static int powerpc__annotate_init(struct arch *arch, char *cpuid __maybe_unused)
> {
> if (!arch->initialized) {
> + arch->nr_instructions = ARRAY_SIZE(powerpc__instructions);
> + arch->instructions = calloc(arch->nr_instructions, sizeof(struct ins));
> + if (arch->instructions == NULL)
> + return -ENOMEM;
> +
> + memcpy(arch->instructions, (struct ins *)powerpc__instructions, sizeof(struct ins) * arch->nr_instructions);
> + arch->nr_instructions_allocated = arch->nr_instructions;
> arch->initialized = true;
> arch->associate_instruction_ops = powerpc__associate_instruction_ops;
> arch->objdump.comment_char      = '#';
> -- 
> 2.43.0
> 


  reply	other threads:[~2024-03-09  7:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09  5:51 [PATCH 0/3] Add data type profiling support for powerpc Athira Rajeev
2024-03-09  5:51 ` [PATCH 1/3] tools/perf/arch/powerpc: Add load/store in powerpc annotate instructions for data type profling Athira Rajeev
2024-03-09  7:18   ` Athira Rajeev [this message]
2024-03-09  5:51 ` [PATCH 2/3] tools/erf/util/annotate: Set register_char and memory_ref_char for powerpc Athira Rajeev
2024-03-09  5:51 ` [PATCH 3/3] tools/perf/arch/powerc: Add get_arch_regnum " Athira Rajeev
2024-03-09  7:25 [PATCH 0/3] Add data type profiling support " Athira Rajeev
2024-03-09  7:25 ` [PATCH 1/3] tools/perf/arch/powerpc: Add load/store in powerpc annotate instructions for data type profling Athira Rajeev
2024-03-09  9:48   ` Christophe Leroy
2024-03-18 11:01     ` Athira Rajeev

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=D1EBC8FF-80A4-4A2A-BEAC-E170EB4400CB@linux.vnet.ibm.com \
    --to=atrajeev@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=disgoel@linux.vnet.ibm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kjain@linux.ibm.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=namhyung@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).