From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
Andi Kleen <andi@firstfloor.org>, Jiri Olsa <jolsa@kernel.org>,
Wang Nan <wangnan0@huawei.com>,
Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Vendor events file/dir names
Date: Tue, 18 Oct 2016 12:36:18 -0300 [thread overview]
Message-ID: <20161018153618.GV12815@kernel.org> (raw)
In-Reply-To: <20161018075901.GB21544@gmail.com>
Em Tue, Oct 18, 2016 at 09:59:01AM +0200, Ingo Molnar escreveu:
> * Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > Ingo pointed out to me that in the kernel sources we do not use
> > file/dir names with uppercase chars (look, for instance, at arch/), so I
> > mostly scripted a conversion to lowercase and what I got is at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/vendor_events
> > Please let me know if you have any technical argument against
> > this move,
>
> Looks good to me!
So I've made this signed tag available with just what is in this branch,
that was based off tip/perf/urgent, please pull it into the most convenient
branch at this time,
Thanks,
- Arnaldo
tag perf-vendor_events-for-mingo-20161018
Tagger: Arnaldo Carvalho de Melo <acme@redhat.com>
Date: Tue Oct 18 11:55:04 2016 -0300
perf/vendor_events event tables:
- Add JSON files with vendor event naming for Intel and Power8
processors,
allowing users of tools like oprofile to keep using the event names
they
are used to, as well as people reading vendor documentation, where
such
naming is used (Andi Kleen, Sukadev Bhattiprolu)
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAABCAAGBQJYBj75AAoJENZQFvNTUqpAP6QP/R/p0UPopmJVql2Ht6cTBi04
K8q25fFyBfzILlHGzGenSL4Q2Rv8poBm5fU7bNVWMHyhRxC8iKElRXd/PD9Cq+7c
doRavPLcOTIqFgmH3xS5pAy3RjhxQU5+0/rPgrbcwA2d7jJm0ThF+sjBSlO6Ppf+
xxYE1sUgNW2KJLy92FZneD/EVILWV7FX/+DaF0dzKD+9cG5DvGjFSY8Z6gMNITs7
SUYvP/E8/8vchr/U55iGl9jcUMhv5oGq3BIGVwtKnigNuvCABsEk01vbaGd+tnU4
iaSG6nI1eyiwqPswBEXrdZLvWIZHz7XkWglNQMCYJG8unSylTCTr2p2Aedl0Wmel
HrR7GRNh0nYhgU7Bp6qnuCKx4Q6WMKTLOle0bDqb6hn47/rfFx0cDfcL8PODQZkK
c8vHFV0M3YgrrFeBLGsPs90ocekXsgX0VPql+7RTMX+X9KGTQPV/u0aEXVHMrjVe
9vVWtrl57KERedg9PnVWbcHB2FXQ6ujyaI/liZyjA/UnYQo8LnkmxrFY0d921ikL
ruCUAwBO47CJC3e77IuCMKAteR3Na5RiY6PFaVvt/On9R2VC2sC07Wufzam7nBGF
3i/agyoHLVMtWC5bLDANTVH0COchq4W1TtQ2u88z0LWidQ6V+G94Q62JnWVEzLu3
/Nw/9EBBSBliCBcJRwB0
=IZAQ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-10-18 15:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 19:04 [RFC] Vendor events file/dir names Arnaldo Carvalho de Melo
2016-10-17 21:26 ` Andi Kleen
2016-10-18 7:59 ` Ingo Molnar
2016-10-18 15:36 ` Arnaldo Carvalho de Melo [this message]
2016-10-19 13:38 ` [GIT PULL] " Ingo Molnar
2016-10-19 14:07 ` Arnaldo Carvalho de Melo
2016-10-19 15:24 ` Ingo Molnar
2016-10-19 16:41 ` Andi Kleen
2016-10-19 17:49 ` Andi Kleen
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=20161018153618.GV12815@kernel.org \
--to=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=sukadev@linux.vnet.ibm.com \
--cc=wangnan0@huawei.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).