From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] perf: Add more syscalls to benchmark
Date: Wed, 28 Sep 2022 11:15:47 -0300 [thread overview]
Message-ID: <YzRXE2JTKrDzHUYL@kernel.org> (raw)
In-Reply-To: <8eed7586-0f47-a576-195f-0180826a67f3@loongson.cn>
Em Wed, Sep 28, 2022 at 09:06:03AM +0800, Tiezhu Yang escreveu:
>
>
> On 09/06/2022 11:06 AM, Tiezhu Yang wrote:
> > Tiezhu Yang (3):
> > perf bench syscall: Introduce bench_syscall_common()
> > perf bench syscall: Add close syscall benchmark
> > perf bench syscall: Add execve syscall benchmark
> >
> > tools/perf/bench/bench.h | 2 ++
> > tools/perf/bench/syscall.c | 76 +++++++++++++++++++++++++++++++++++++++++++---
> > tools/perf/builtin-bench.c | 2 ++
> > 3 files changed, 76 insertions(+), 4 deletions(-)
> >
>
> Hi all,
>
> Any more comments? Do you think this patch series [1] is useful?
> If yes, I will send v2 to fix the build error about undeclared
> __NR_getppid reported by kernel test robot.
>
> [1] https://lore.kernel.org/lkml/1662433577-23266-1-git-send-email-yangtiezhu@loongson.cn/
Please send the v2.
- Arnaldo
prev parent reply other threads:[~2022-09-28 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 3:06 [PATCH 0/3] perf: Add more syscalls to benchmark Tiezhu Yang
2022-09-06 3:06 ` [PATCH 1/3] perf bench syscall: Introduce bench_syscall_common() Tiezhu Yang
2022-09-06 3:06 ` [PATCH 2/3] perf bench syscall: Add close syscall benchmark Tiezhu Yang
2022-09-06 3:30 ` David Laight
2022-09-06 4:27 ` Tiezhu Yang
2022-09-06 3:06 ` [PATCH 3/3] perf bench syscall: Add execve " Tiezhu Yang
2022-09-28 1:06 ` [PATCH 0/3] perf: Add more syscalls to benchmark Tiezhu Yang
2022-09-28 14:15 ` Arnaldo Carvalho de Melo [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=YzRXE2JTKrDzHUYL@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yangtiezhu@loongson.cn \
/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).