mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Wang Nan <wangnan0@huawei.com>
To: <acme@kernel.org>, <masami.hiramatsu.pt@hitachi.com>
Cc: <linux-kernel@vger.kernel.org>, <ast@kernel.org>,
	<namhyung@kernel.org>, <lizefan@huawei.com>, <pi3orama@163.com>,
	Wang Nan <wangnan0@huawei.com>
Subject: [PATCH v3 0/2] perf tools: Builtin options related improvements
Date: Fri, 27 Nov 2015 05:36:28 +0000	[thread overview]
Message-ID: <1448602590-194992-1-git-send-email-wangnan0@huawei.com> (raw)

According to Arnaldo's suggestion, patch 1/2 ensures options always
there even if they are not build. When user tries to use a not build
option, error or warning messages would tell them the reason.

Patch 2/2 adds vmlinux option to perf record to support BPF argument
fetching better. Without this patch vmlinux must be reside in standard
path for BPF loader finding it.

He Kuang (1):
  perf record: Support custom vmlinux path

Wang Nan (1):
  perf tools: Always give options even it not compiled

 tools/perf/Documentation/perf-record.txt |  10 ++-
 tools/perf/builtin-probe.c               |  15 +++-
 tools/perf/builtin-record.c              |  25 ++++++-
 tools/perf/util/parse-options.c          | 113 ++++++++++++++++++++++++++++---
 tools/perf/util/parse-options.h          |   5 ++
 5 files changed, 153 insertions(+), 15 deletions(-)

-- 
1.8.3.4


             reply	other threads:[~2015-11-27  5:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27  5:36 Wang Nan [this message]
2015-11-27  5:36 ` [PATCH v3 1/2] perf tools: Always give options even it not compiled Wang Nan
2015-11-27  5:36 ` [PATCH v3 2/2] perf record: Support custom vmlinux path 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=1448602590-194992-1-git-send-email-wangnan0@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=masami.hiramatsu.pt@hitachi.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

all inboxes | Powered by JetHome®