[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <be1a7df0-866d-352f-846a-e5a73500b172@linux.intel.com>
Date: Fri, 9 Apr 2021 10:06:08 +0300
From: "Bayduraev, Alexey V" <alexey.v.bayduraev@...ux.intel.com>
To: Andi Kleen <ak@...ux.intel.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Alexei Budankov <abudankov@...wei.com>,
Alexander Antonov <alexander.antonov@...ux.intel.com>
Subject: Re: [PATCH v4 02/12] perf record: introduce thread specific data
array
Hi,
On 08.04.2021 17:16, Andi Kleen wrote:
>> + } else {
>> + thread_data[t].tid = syscall(SYS_gettid);
>
> That always fills in the tid of the setup thread instead of the target
> threads?
>
Here we set the tid for 0-thread (for cpu 0), other threads we setup
later in record__thread(), see [PATCH v4 05/12].
Regards,
Alexey
Powered by blists - more mailing lists