All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Hari Bathini <hbathini@linux.vnet.ibm.com>
Cc: ast@fb.com, peterz@infradead.org,
	lkml <linux-kernel@vger.kernel.org>,
	acme@kernel.org, alexander.shishkin@linux.intel.com,
	mingo@redhat.com, daniel@iogearbox.net, rostedt@goodmis.org,
	Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
	ebiederm@xmission.com, sargun@sargun.me,
	Aravinda Prasad <aravinda@linux.vnet.ibm.com>,
	brendan.d.gregg@gmail.com
Subject: Re: [PATCH v5 2/3] perf tool: add PERF_RECORD_NAMESPACES to include namespaces related info
Date: Wed, 18 Jan 2017 14:14:01 +0100	[thread overview]
Message-ID: <20170118131401.GB22162@krava> (raw)
In-Reply-To: <148466265189.32153.11889447823332171550.stgit@hbathini.in.ibm.com>

On Tue, Jan 17, 2017 at 07:47:38PM +0530, Hari Bathini wrote:
> This patch updates perf tool to examine PERF_RECORD_NAMESPACES events
> emitted by the kernel when fork, clone, setns or unshare are invoked.
> Also, it synthesizes PERF_RECORD_NAMESPACES events for processes that
> were running prior to invocation of perf record, the data for which
> is taken from /proc/$PID/ns. These changes make way for analyzing
> events with regard to namespaces.
> 
> Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>

could you please rebase this on latest Arnaldo's perf/core?
I've got following conflicts:

patching file tools/include/uapi/linux/perf_event.h
patching file tools/perf/builtin-annotate.c
patching file tools/perf/builtin-diff.c
patching file tools/perf/builtin-inject.c
patching file tools/perf/builtin-kmem.c
Hunk #1 succeeded at 965 (offset 1 line).
patching file tools/perf/builtin-kvm.c
patching file tools/perf/builtin-lock.c
patching file tools/perf/builtin-mem.c
patching file tools/perf/builtin-record.c
Hunk #1 FAILED at 842.
Hunk #2 succeeded at 982 (offset 33 lines).
Hunk #3 succeeded at 996 (offset 33 lines).
Hunk #4 succeeded at 1515 (offset 109 lines).
Hunk #5 succeeded at 1630 (offset 109 lines).
1 out of 5 hunks FAILED -- saving rejects to file tools/perf/builtin-record.c.rej
patching file tools/perf/builtin-report.c
patching file tools/perf/builtin-sched.c
Hunk #1 succeeded at 3272 (offset 105 lines).
patching file tools/perf/builtin-script.c
Hunk #5 FAILED at 2219.
1 out of 5 hunks FAILED -- saving rejects to file tools/perf/builtin-script.c.rej
patching file tools/perf/builtin-trace.c
Hunk #1 succeeded at 2415 (offset 1 line).
patching file tools/perf/perf.h
patching file tools/perf/util/Build
patching file tools/perf/util/data-convert-bt.c
patching file tools/perf/util/event.c
patching file tools/perf/util/event.h
patching file tools/perf/util/evsel.c
patching file tools/perf/util/machine.c
Hunk #2 succeeded at 502 (offset 19 lines).
Hunk #3 succeeded at 1570 (offset 19 lines).
patching file tools/perf/util/machine.h
patching file tools/perf/util/namespaces.c
patching file tools/perf/util/namespaces.h
patching file tools/perf/util/session.c
patching file tools/perf/util/thread.c
patching file tools/perf/util/thread.h
patching file tools/perf/util/tool.h


thanks,
jirka

  reply	other threads:[~2017-01-18 13:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-17 14:16 [PATCH v5 0/3] perf: add support for analyzing events for containers Hari Bathini
2017-01-17 14:17 ` [PATCH v5 1/3] perf: add PERF_RECORD_NAMESPACES to include namespaces related info Hari Bathini
2017-01-18 14:26   ` Peter Zijlstra
2017-01-20 15:56     ` Hari Bathini
2017-01-20 16:54       ` Peter Zijlstra
2017-01-17 14:17 ` [PATCH v5 2/3] perf tool: " Hari Bathini
2017-01-18 13:14   ` Jiri Olsa [this message]
2017-01-17 14:18 ` [PATCH v5 3/3] perf tool: add cgroup identifier entry in perf report Hari Bathini

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=20170118131401.GB22162@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ananth@linux.vnet.ibm.com \
    --cc=aravinda@linux.vnet.ibm.com \
    --cc=ast@fb.com \
    --cc=brendan.d.gregg@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=ebiederm@xmission.com \
    --cc=hbathini@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sargun@sargun.me \
    /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.