netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
	Yonghong Song <yhs@fb.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Mike Leach <mike.leach@linaro.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH v1 0/4] perf augmented_raw_syscalls: Support for arm64
Date: Thu, 6 Jun 2019 17:52:02 +0800	[thread overview]
Message-ID: <20190606095202.GA5970@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <20190606075617.14327-1-leo.yan@linaro.org>

Hi all,

On Thu, Jun 06, 2019 at 03:56:13PM +0800, Leo Yan wrote:
> When I tried to run the trace on arm64 platform with eBPF program
> augmented_raw_syscalls, it reports several failures for eBPF program
> compilation.  So tried to resolve these issues and this patch set is
> the working result.
> 
> 0001 patch lets perf command to exit directly if find eBPF program
> building failure.
> 
> 0002 patch is minor refactoring code to remove duplicate macro.
> 
> 0003 patch is to add support arm64 raw syscalls numbers.

I found minor issues in patch 0003, so sent out v2 for reviewing.

Sorry for spamming.

Thanks,
Leo Yan

> 0004 patch is to document clang configuration so that can easily use
> this program on both x86_64 and aarch64 platforms.
> 
> 
> Leo Yan (4):
>   perf trace: Exit when build eBPF program failure
>   perf augmented_raw_syscalls: Remove duplicate macros
>   perf augmented_raw_syscalls: Support arm64 raw syscalls
>   perf augmented_raw_syscalls: Document clang configuration
> 
>  tools/perf/builtin-trace.c                    |   8 ++
>  .../examples/bpf/augmented_raw_syscalls.c     | 102 +++++++++++++++++-
>  2 files changed, 109 insertions(+), 1 deletion(-)
> 
> -- 
> 2.17.1
> 

      parent reply	other threads:[~2019-06-06  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06  7:56 [PATCH v1 0/4] perf augmented_raw_syscalls: Support for arm64 Leo Yan
2019-06-06  7:56 ` [PATCH v1 1/4] perf trace: Exit when build eBPF program failure Leo Yan
2019-06-06  7:56 ` [PATCH v1 2/4] perf augmented_raw_syscalls: Remove duplicate macros Leo Yan
2019-06-06  7:56 ` [PATCH v1 3/4] perf augmented_raw_syscalls: Support arm64 raw syscalls Leo Yan
2019-06-06  7:56 ` [PATCH v1 4/4] perf augmented_raw_syscalls: Document clang configuration Leo Yan
2019-06-06  9:52 ` Leo Yan [this message]

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=20190606095202.GA5970@leoy-ThinkPad-X240s \
    --to=leo.yan@linaro.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jolsa@redhat.com \
    --cc=kafai@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=namhyung@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=suzuki.poulose@arm.com \
    --cc=yhs@fb.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).