From: Hangliang Lai <laihangliang1@huawei.com>
To: <namhyung@kernel.org>
Cc: <acme@kernel.org>, <adrian.hunter@intel.com>,
<alexander.shishkin@linux.intel.com>, <brauner@kernel.org>,
<hewenliang4@huawei.com>, <irogers@google.com>,
<jolsa@kernel.org>, <laihangliang1@huawei.com>,
<linfeilong@huawei.com>, <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <liuwenyu7@huawei.com>,
<mark.rutland@arm.com>, <mingo@redhat.com>,
<yeyunfeng@huawei.com>
Subject: Re: [PATCH v2] perf top: expand the range of multithreaded phase
Date: Mon, 10 Apr 2023 10:58:08 +0800 [thread overview]
Message-ID: <20230410025808.2008-1-laihangliang1@huawei.com> (raw)
In-Reply-To: <CAM9d7cgK-P5KuDy7hkAR4j7oB4ydE6Mw3KexqgwPPhJF6MKtXQ@mail.gmail.com>
Thanks for your reply Kim ,
On 2023-04-07 21:21 you wrote:
> Not always, the synthesis can run in a single thread.
But I think in machine__synthesize_threads, there are thread_nr threads will be created to do synthesize_threads_worker(tools/perf/util/synthetic-events.c:970)
Itâs not a single thread part. So we're supposed to call perf_set_multithreaded() before synthesize?
Thanks,
Hangliang Lai
next prev parent reply other threads:[~2023-04-10 2:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 10:05 [PATCH] " Hangliang Lai
2023-04-01 0:11 ` Namhyung Kim
2023-04-06 2:53 ` [PATCH v2] " Hangliang Lai
2023-04-07 21:21 ` Namhyung Kim
2023-04-10 2:58 ` Hangliang Lai [this message]
2023-04-10 3:38 ` Wenyu Liu(D)
2023-04-10 13:22 ` [PATCH v3] " Hangliang Lai
2023-04-10 15:36 ` Namhyung Kim
2023-04-11 1:32 ` [PATCH v4] " Hangliang Lai
2023-04-12 13:39 ` 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=20230410025808.2008-1-laihangliang1@huawei.com \
--to=laihangliang1@huawei.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=brauner@kernel.org \
--cc=hewenliang4@huawei.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linfeilong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=liuwenyu7@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=yeyunfeng@huawei.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®