From: "Wangnan (F)" <wangnan0@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: <namhyung@kernel.org>, <lizefan@huawei.com>, <pi3orama@163.com>,
<linux-kernel@vger.kernel.org>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH 1/4] perf tools: Pass available CPU number to clang compiler
Date: Thu, 5 Nov 2015 09:41:27 +0800 [thread overview]
Message-ID: <563AB3C7.2010600@huawei.com> (raw)
In-Reply-To: <20151104220953.GL13236@kernel.org>
On 2015/11/5 6:09, Arnaldo Carvalho de Melo wrote:
> Em Wed, Nov 04, 2015 at 11:20:04AM +0000, Wang Nan escreveu:
>> This patch introduces a new macro "__NR_CPUS__" to perf's embedded
>> clang compiler, which represent the available CPU counters in this
> available "CPU counters"? ENOPARSE :-)
Your changing is better.
This patch is for support Alexei's BPF output and Xia Kaixu's BPF
pmu reading. In these cases we need to create an array with
same number of slots with system CPUs.
Thank you.
next prev parent reply other threads:[~2015-11-05 1:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 11:20 [PATCH 0/4] perf tools: Improve llvm compiling and test Wang Nan
2015-11-04 11:20 ` [PATCH 1/4] perf tools: Pass available CPU number to clang compiler Wang Nan
2015-11-04 22:09 ` Arnaldo Carvalho de Melo
2015-11-05 1:41 ` Wangnan (F) [this message]
2015-11-08 7:29 ` [tip:perf/urgent] perf llvm: Pass number of configured CPUs " tip-bot for Wang Nan
2015-11-04 11:20 ` [PATCH 2/4] perf tools: Pass LINUX_VERSION_CODE to BPF program when compiling Wang Nan
2015-11-04 22:23 ` Arnaldo Carvalho de Melo
2015-11-08 7:30 ` [tip:perf/urgent] perf llvm: " tip-bot for Wang Nan
2015-11-04 11:20 ` [PATCH 3/4] perf test: Enforce LLVM test: update basic BPF test program Wang Nan
2015-11-04 22:23 ` Arnaldo Carvalho de Melo
2015-11-04 11:20 ` [PATCH 4/4] perf test: Enforce LLVM test: add kbuild test Wang Nan
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=563AB3C7.2010600@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@kernel.org \
--cc=ast@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=namhyung@kernel.org \
--cc=pi3orama@163.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