From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v5 0/4] perf: Add more syscalls to benchmark
Date: Sat, 7 Jan 2023 15:23:27 +0800 [thread overview]
Message-ID: <06c8a265-0120-c4e1-6032-7bb3190df90a@loongson.cn> (raw)
In-Reply-To: <CAM9d7cgH0zK-DUmUV7yw1BJBvgyxWys9zPuB5Q7dQQwta=XcGA@mail.gmail.com>
On 01/07/2023 05:04 AM, Namhyung Kim wrote:
> Hello,
>
> On Thu, Jan 5, 2023 at 5:23 PM Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
>>
>>
>>
>> On 12/03/2022 05:19 PM, Tiezhu Yang wrote:
>>>
>>>
>>> On 11/10/2022 11:50 AM, Tiezhu Yang wrote:
>>>> Tested on x86_64, arm64, mips64 and loongarch64.
>>>>
>>>> Tiezhu Yang (4):
>>>> tools x86: Keep list sorted by number in unistd_{32,64}.h
>>>> perf bench syscall: Introduce bench_syscall_common()
>>>> perf bench syscall: Add getpgid syscall benchmark
>>>> perf bench syscall: Add execve syscall benchmark
>>>>
>>>> tools/arch/x86/include/uapi/asm/unistd_32.h | 23 ++++++---
>>>> tools/arch/x86/include/uapi/asm/unistd_64.h | 23 ++++++---
>>>> tools/perf/bench/bench.h | 2 +
>>>> tools/perf/bench/syscall.c | 76
>>>> +++++++++++++++++++++++++++--
>>>> tools/perf/builtin-bench.c | 2 +
>>>> 5 files changed, 108 insertions(+), 18 deletions(-)
>>>>
>>>
>>> Ping, any more comments?
>>>
>>> Thanks,
>>> Tiezhu
>>
>> Hi all,
>>
>> If this patch series has no value and is not acceptable,
>> or what should I do to update, please let me know.
>
> I'm so sorry about being late a lot.
> I don't have any objection to this series.
>
> For the execve bench, I think it's actually fork + execve
> then maybe it makes sense to have a fork only bench
> to compare the execve part precisely.
>
> But it can be added later, so
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
>
> Thanks,
> Namhyung
>
Hi Namhyung,
Thank you very much. I will submit another single patch
to benchmark fork after this series is applied.
Thanks,
Tiezhu
next prev parent reply other threads:[~2023-01-07 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 3:50 Tiezhu Yang
2022-11-10 3:50 ` [PATCH v5 1/4] tools x86: Keep list sorted by number in unistd_{32,64}.h Tiezhu Yang
2022-11-10 3:50 ` [PATCH v5 2/4] perf bench syscall: Introduce bench_syscall_common() Tiezhu Yang
2022-11-10 3:50 ` [PATCH v5 3/4] perf bench syscall: Add getpgid syscall benchmark Tiezhu Yang
2022-11-10 3:50 ` [PATCH v5 4/4] perf bench syscall: Add execve " Tiezhu Yang
2022-12-03 9:19 ` [PATCH v5 0/4] perf: Add more syscalls to benchmark Tiezhu Yang
2023-01-06 0:17 ` Tiezhu Yang
2023-01-06 21:04 ` Namhyung Kim
2023-01-07 7:23 ` Tiezhu Yang [this message]
2023-02-02 1:58 ` Arnaldo Carvalho de Melo
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=06c8a265-0120-c4e1-6032-7bb3190df90a@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=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 \
/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®