From: Michael Ellerman <mpe@ellerman.id.au>
To: Chandan Kumar <chandan.kumar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: maddy@linux.vnet.ibm.com, acme@redhat.com,
hemant@linux.vnet.ibm.com, anju@linux.vnet.ibm.com,
naveen.n.rao@linux.vnet.ibm.com, jolsa@redhat.com
Subject: Re: [3/3] perf tools: Fix perf regs mask generation
Date: Sun, 8 May 2016 13:59:34 +1000 (AEST) [thread overview]
Message-ID: <3r2Wx26Hdtz9t0r@ozlabs.org> (raw)
In-Reply-To: <1461835870-67778-4-git-send-email-chandan.kumar@linux.vnet.ibm.com>
On Thu, 2016-28-04 at 09:31:10 UTC, Chandan Kumar wrote:
> From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
>
> On some architectures (powerpc in particular), the number of registers
> exceeds what can be represented in an integer bitmask. Ensure we
> generate the proper bitmask on such platforms.
>
> Fixes: 71ad0f5e4 ("perf tools: Support for DWARF CFI unwinding on post
> processing")
>
> Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/826dccfd238c3eeac379f5f637
cheers
next prev parent reply other threads:[~2016-05-08 3:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 9:31 [PATCH 0/3] Add support for perf user stack dump in powerpc Chandan Kumar
2016-04-28 9:31 ` [PATCH 1/3] powerpc: Add HAVE_PERF_USER_STACK_DUMP support Chandan Kumar
2016-05-08 3:59 ` [1/3] " Michael Ellerman
2016-04-28 9:31 ` [PATCH 2/3] powerpc/perf: Add support for unwinding perf-stackdump Chandan Kumar
2016-05-08 3:59 ` [2/3] " Michael Ellerman
2016-04-28 9:31 ` [PATCH 3/3] perf tools: Fix perf regs mask generation Chandan Kumar
2016-05-08 3:59 ` Michael Ellerman [this message]
2016-04-28 14:23 ` [PATCH 0/3] Add support for perf user stack dump in powerpc Naveen N. Rao
2016-04-28 15:29 ` Arnaldo Carvalho de Melo
2016-04-28 16:14 ` Naveen N. Rao
2016-04-28 16:31 ` Arnaldo Carvalho de Melo
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=3r2Wx26Hdtz9t0r@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=acme@redhat.com \
--cc=anju@linux.vnet.ibm.com \
--cc=chandan.kumar@linux.vnet.ibm.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=naveen.n.rao@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).