linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Anju T <anju@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mpe@ellerman.id.au,
	maddy@linux.vnet.ibm.com, jolsa@redhat.com, dsahern@gmail.com,
	acme@redhat.com, sukadev@linux.vnet.ibm.com,
	hemant@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V11 1/4] perf/powerpc: assign an id to each powerpc register
Date: Thu, 21 Apr 2016 16:37:36 +0530	[thread overview]
Message-ID: <20160421110736.GC28637@naverao1-tp.ibm.com> (raw)
In-Reply-To: <1455944568-7231-2-git-send-email-anju@linux.vnet.ibm.com>

On 2016/02/20 10:32AM, Anju T wrote:
> The enum definition assigns an 'id' to each register in "struct pt_regs"
> of arch/powerpc. The order of these values in the enum definition are
> based on the corresponding macros in arch/powerpc/include/uapi/asm/ptrace.h.
> 
> Signed-off-by: Anju T <anju@linux.vnet.ibm.com>
> ---
>  arch/powerpc/include/uapi/asm/perf_regs.h | 50 +++++++++++++++++++++++++++++++
>  1 file changed, 50 insertions(+)
>  create mode 100644 arch/powerpc/include/uapi/asm/perf_regs.h

This patch doesn't enable anything and doesn't look to be useful by 
itself. Please merge this with your second patch.

- Naveen

> 
> diff --git a/arch/powerpc/include/uapi/asm/perf_regs.h b/arch/powerpc/include/uapi/asm/perf_regs.h
> new file mode 100644
> index 0000000..62b8a5e
> --- /dev/null
> +++ b/arch/powerpc/include/uapi/asm/perf_regs.h
> @@ -0,0 +1,50 @@
> +#ifndef _ASM_POWERPC_PERF_REGS_H
> +#define _ASM_POWERPC_PERF_REGS_H
> +
> +enum perf_event_powerpc_regs {
> +	PERF_REG_POWERPC_R0,
> +	PERF_REG_POWERPC_R1,
> +	PERF_REG_POWERPC_R2,
> +	PERF_REG_POWERPC_R3,
> +	PERF_REG_POWERPC_R4,
> +	PERF_REG_POWERPC_R5,
> +	PERF_REG_POWERPC_R6,
> +	PERF_REG_POWERPC_R7,
> +	PERF_REG_POWERPC_R8,
> +	PERF_REG_POWERPC_R9,
> +	PERF_REG_POWERPC_R10,
> +	PERF_REG_POWERPC_R11,
> +	PERF_REG_POWERPC_R12,
> +	PERF_REG_POWERPC_R13,
> +	PERF_REG_POWERPC_R14,
> +	PERF_REG_POWERPC_R15,
> +	PERF_REG_POWERPC_R16,
> +	PERF_REG_POWERPC_R17,
> +	PERF_REG_POWERPC_R18,
> +	PERF_REG_POWERPC_R19,
> +	PERF_REG_POWERPC_R20,
> +	PERF_REG_POWERPC_R21,
> +	PERF_REG_POWERPC_R22,
> +	PERF_REG_POWERPC_R23,
> +	PERF_REG_POWERPC_R24,
> +	PERF_REG_POWERPC_R25,
> +	PERF_REG_POWERPC_R26,
> +	PERF_REG_POWERPC_R27,
> +	PERF_REG_POWERPC_R28,
> +	PERF_REG_POWERPC_R29,
> +	PERF_REG_POWERPC_R30,
> +	PERF_REG_POWERPC_R31,
> +	PERF_REG_POWERPC_NIP,
> +	PERF_REG_POWERPC_MSR,
> +	PERF_REG_POWERPC_ORIG_R3,
> +	PERF_REG_POWERPC_CTR,
> +	PERF_REG_POWERPC_LNK,
> +	PERF_REG_POWERPC_XER,
> +	PERF_REG_POWERPC_CCR,
> +	PERF_REG_POWERPC_SOFTE,
> +	PERF_REG_POWERPC_TRAP,
> +	PERF_REG_POWERPC_DAR,
> +	PERF_REG_POWERPC_DSISR,
> +	PERF_REG_POWERPC_MAX,
> +};
> +#endif /* _ASM_POWERPC_PERF_REGS_H */
> -- 
> 2.1.0
> 

  reply	other threads:[~2016-04-21 11:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20  5:02 [PATCH V11 0/4]perf/powerpc: Add ability to sample intr machine state in powerpc Anju T
2016-02-20  5:02 ` [PATCH V11 1/4] perf/powerpc: assign an id to each powerpc register Anju T
2016-04-21 11:07   ` Naveen N. Rao [this message]
2016-04-21 13:39   ` [V11,1/4] " Michael Ellerman
2016-02-20  5:02 ` [PATCH V11 2/4] perf/powerpc: add support for sampling intr machine state Anju T
2016-04-21 11:15   ` Naveen N. Rao
2016-04-21 13:39   ` [V11, " Michael Ellerman
2016-02-20  5:02 ` [PATCH V11 3/4] tools/perf: Map the ID values with register names Anju T
2016-04-21 13:39   ` [V11,3/4] " Michael Ellerman
2016-02-20  5:02 ` [PATCH V2 4/4] tool/perf: Add sample_reg_mask to include all perf_regs Anju T
2016-04-21 13:39   ` [V2,4/4] " Michael Ellerman
2016-03-07  8:23 ` [PATCH V11 0/4]perf/powerpc: Add ability to sample intr machine state in powerpc Anju T
2016-04-18  9:47 ` Anju T
2016-04-20  3:57   ` Arnaldo Carvalho de Melo
2016-04-20  4:55     ` Michael Ellerman
2016-04-20 13:16       ` Arnaldo Carvalho de Melo
2016-04-21 13:41         ` Michael Ellerman

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=20160421110736.GC28637@naverao1-tp.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=acme@redhat.com \
    --cc=anju@linux.vnet.ibm.com \
    --cc=dsahern@gmail.com \
    --cc=hemant@linux.vnet.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=sukadev@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).