From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Andi Kleen <ak@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 0/2]: perf: reduce data loss when profiling highly parallel CPU bound workloads
Date: Thu, 6 Sep 2018 11:20:20 +0300 [thread overview]
Message-ID: <9c3fd200-e2e8-3cf1-09b0-c89bafc76750@linux.intel.com> (raw)
In-Reply-To: <20180906081438.GB8248@krava>
Hi,
On 06.09.2018 11:14, Jiri Olsa wrote:
> On Thu, Sep 06, 2018 at 09:03:17AM +0300, Alexey Budankov wrote:
>> Hi,
>>
>> On 05.09.2018 21:51, Arnaldo Carvalho de Melo wrote:
>>> Em Wed, Sep 05, 2018 at 08:37:32PM +0300, Alexey Budankov escreveu:
>>>> On 05.09.2018 14:28, Jiri Olsa wrote:
>>>>> can't apply this version on Arnaldo's perf/core...
>>>
>>>> my git remote -v
>>>
>>>> origin git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (fetch)
>>>> origin git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (push)
>>>
>>>> branch is perf/core, according to MAINTAINERS content.
>>>
>>>> What is Arnaldo's perf/core? This one?
>>>
>>>> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux
>>>
>>>> and branch is perf/core?
>>>
>>> yes.
>>
>> Is this the actual one for the tool development? Am I missing something?
>
> yep, Arnaldo takes all and pushes his perf/core to Ingo
> it's better to always rebase to it
Good to know. Thanks!
>
> thanks,
> jirka
>
next prev parent reply other threads:[~2018-09-06 8:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 7:16 Alexey Budankov
2018-09-05 7:19 ` [PATCH v7 1/2]: perf util: map data buffer for preserving collected data Alexey Budankov
2018-09-06 11:04 ` Jiri Olsa
2018-09-06 11:50 ` Alexey Budankov
2018-09-06 11:04 ` Jiri Olsa
2018-09-06 11:54 ` Alexey Budankov
2018-09-05 7:39 ` [PATCH v7 2/2]: perf record: enable asynchronous trace writing Alexey Budankov
2018-09-06 11:04 ` Jiri Olsa
2018-09-06 11:57 ` Alexey Budankov
2018-09-06 11:04 ` Jiri Olsa
2018-09-06 11:58 ` Alexey Budankov
2018-09-06 11:04 ` Jiri Olsa
2018-09-06 11:59 ` Alexey Budankov
2018-09-06 11:04 ` Jiri Olsa
2018-09-06 12:09 ` Alexey Budankov
2018-09-05 11:28 ` [PATCH v7 0/2]: perf: reduce data loss when profiling highly parallel CPU bound workloads Jiri Olsa
2018-09-05 17:37 ` Alexey Budankov
2018-09-05 18:51 ` Arnaldo Carvalho de Melo
2018-09-06 6:03 ` Alexey Budankov
2018-09-06 8:14 ` Jiri Olsa
2018-09-06 8:20 ` Alexey Budankov [this message]
2018-09-06 6:59 ` Alexey Budankov
2018-09-06 6:57 ` Alexey Budankov
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=9c3fd200-e2e8-3cf1-09b0-c89bafc76750@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome