From: Anju T Sudhakar <anju@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: mpe@ellerman.id.au, anju@linux.vnet.ibm.com, acme@kernel.org,
linux-kernel@vger.kernel.org, maddy@linux.vnet.ibm.com,
ravi.bangoria@linux.ibm.com, jolsa@kernel.org
Subject: [PATCH 1/2] tools/perf: set no_auxtrace for powerpc
Date: Wed, 29 Apr 2020 11:34:14 +0530 [thread overview]
Message-ID: <20200429060415.25930-2-anju@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200429060415.25930-1-anju@linux.vnet.ibm.com>
x86/perf_regs.h is included by util/intel-pt.c, which will get compiled
when buiding perf on powerpc. Since x86/perf_regs.h has
`PERF_EXTENDED_REG_MASK` defined, defining `PERF_EXTENDED_REG_MASK` for
powerpc to add support for perf extended regs will result in perf build
error on powerpc.
Currently powerpc architecture is not having support for auxtrace. So as
a workaround for this issue, set NO_AUXTRACE for powerpc.
Signed-off-by: Anju T Sudhakar <anju@linux.vnet.ibm.com>
---
tools/perf/arch/powerpc/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/arch/powerpc/Makefile b/tools/perf/arch/powerpc/Makefile
index e58d00d62f02..9ebb5f513605 100644
--- a/tools/perf/arch/powerpc/Makefile
+++ b/tools/perf/arch/powerpc/Makefile
@@ -3,6 +3,7 @@ ifndef NO_DWARF
PERF_HAVE_DWARF_REGS := 1
endif
+NO_AUXTRACE := 1
HAVE_KVM_STAT_SUPPORT := 1
PERF_HAVE_ARCH_REGS_QUERY_REGISTER_OFFSET := 1
PERF_HAVE_JITDUMP := 1
--
2.20.1
next prev parent reply other threads:[~2020-04-29 6:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 6:04 [PATCH 0/2] powerpc/perf: Add support for perf extended regs in powerpc Anju T Sudhakar
2020-04-29 6:04 ` Anju T Sudhakar [this message]
2020-04-29 6:04 ` [PATCH 2/2] powerpc/perf: Add support for outputting extended regs in perf intr_regs Anju T Sudhakar
2020-05-05 10:31 ` Ravi Bangoria
2020-05-06 4:26 ` Madhavan Srinivasan
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=20200429060415.25930-2-anju@linux.vnet.ibm.com \
--to=anju@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=ravi.bangoria@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;
as well as URLs for NNTP newsgroup(s).