[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230410025808.2008-1-laihangliang1@huawei.com>
Date: Mon, 10 Apr 2023 10:58:08 +0800
From: Hangliang Lai <laihangliang1@...wei.com>
To: <namhyung@...nel.org>
CC: <acme@...nel.org>, <adrian.hunter@...el.com>,
<alexander.shishkin@...ux.intel.com>, <brauner@...nel.org>,
<hewenliang4@...wei.com>, <irogers@...gle.com>, <jolsa@...nel.org>,
<laihangliang1@...wei.com>, <linfeilong@...wei.com>,
<linux-kernel@...r.kernel.org>, <linux-perf-users@...r.kernel.org>,
<liuwenyu7@...wei.com>, <mark.rutland@....com>, <mingo@...hat.com>,
<yeyunfeng@...wei.com>
Subject: Re: [PATCH v2] perf top: expand the range of multithreaded phase
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
Powered by blists - more mailing lists