From: Wang Nan <wangnan0@huawei.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: <jolsa@kernel.org>, <acme@kernel.org>, <namhyung@kernel.org>,
<lizefan@huawei.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RESEND] perf tools: introduce arm64 support unwind test.
Date: Tue, 21 Apr 2015 11:02:13 +0800 [thread overview]
Message-ID: <5535BDB5.6080709@huawei.com> (raw)
In-Reply-To: <20150330070259.GB1413@krava>
On 2015/3/30 15:03, Jiri Olsa wrote:
> On Mon, Mar 30, 2015 at 02:04:08AM +0000, Wang Nan wrote:
>> Newest libunwind does support ARM64, and perf is able to utilize it
>> also. This patch enables the missing perf test dwarf unwind for arm64.
>>
>> Test result:
>> # ./perf test unwind
>> 25: Test dwarf unwind : Ok
>>
>> Signed-off-by: Wang Nan <wangnan0@huawei.com>
>
> cannot try, but looks ok and match closely x86 pattern ;-)
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
>
> thanks,
> jirka
>
Sorry, I'm unable to find this patch in git repo (both tip/master and mainline).
Is there any problem?
prev parent reply other threads:[~2015-04-21 3:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 2:04 [PATCH RESEND] perf tools: introduce arm64 support unwind test Wang Nan
2015-03-30 7:03 ` Jiri Olsa
2015-04-21 3:02 ` Wang Nan [this message]
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=5535BDB5.6080709@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.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