From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: sukadev@linux.vnet.ibm.com, acme@kernel.org, namhyung@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: perf, tools: Event files for Intel x86
Date: Fri, 22 May 2015 19:27:15 +0200 [thread overview]
Message-ID: <20150522172715.GA16703@krava.redhat.com> (raw)
In-Reply-To: <20150522152011.GG19417@two.firstfloor.org>
On Fri, May 22, 2015 at 05:20:11PM +0200, Andi Kleen wrote:
> > > Currently only core events are included, not uncore.
> >
> > hum, not sure how you guys want to handle this, but it'd be nice
> > to have all the bits in one place.. Could one of you guys please
> > arrange branch with all this?
>
> I would suggest to handle the code together in a single branch.
> And then handle the events separately per architecture, just as pull
> requests without posting. I doubt anyone on linux-kernel would be happy
> about getting that large files in mail; in fact the list software
> may not allow it.
sounds good
jirka
next prev parent reply other threads:[~2015-05-22 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 4:11 perf, tools: Event files for Intel x86 Andi Kleen
2015-05-21 4:11 ` [PATCH 1/6] perf, tools: Handle header line in mapfile Andi Kleen
2015-05-21 4:11 ` [PATCH 2/6] perf, tools: Allow events with dot Andi Kleen
2015-05-21 4:11 ` [PATCH 3/6] perf, tools: Support CPU id matching for x86 Andi Kleen
2015-05-21 4:11 ` [PATCH 4/6] perf, tools: Support alias descriptions Andi Kleen
2015-05-21 4:11 ` [PATCH 5/6] perf, tools: Query terminal width and use in perf list Andi Kleen
2015-05-21 4:11 ` [PATCH 6/6] perf, tools: Add a --no-desc flag to " Andi Kleen
2015-05-22 15:02 ` perf, tools: Event files for Intel x86 Jiri Olsa
2015-05-22 15:20 ` Andi Kleen
2015-05-22 17:27 ` Jiri Olsa [this message]
2015-05-22 16:00 ` Sukadev Bhattiprolu
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=20150522172715.GA16703@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sukadev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.