[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4ded2d63-03dd-498e-9810-690a9eff0c22@lucifer.local>
Date: Fri, 20 Dec 2024 09:31:07 +0000
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: "Chen, Zide" <zide.chen@...el.com>
Cc: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Matthew Wilcox <willy@...radead.org>,
David Hildenbrand <david@...hat.com>, Yi Lai <yi1.lai@...ux.intel.com>
Subject: Re: [PATCH v3] perf: map pages in advance
On Thu, Dec 19, 2024 at 01:17:44PM -0800, Chen, Zide wrote:
> With this patch, it seems perf tool has some problems in capturing the
> kernel data with Intel PT.
>
> Running the following commands, the size of perf.data is very small, and
> perf script can't find any valid records.
>
> perf record -e intel_pt//u -- /bin/ls
> perf script --insn-trace
>
>
Hi,
I'm on leave (and should really go back to relaxing :>), returning on 2nd
Jan so can't really dig into this.
But I tried it on my intel box and it 'works on my machine' with and
without patch with commands provided, so I'm not sure this is actually a
product of this change (which shouldn't impact this).
I'm afraid I can't really reply any further until the new year, however (I
really shouldn't even be replying here ;).
Happy holidays, Lorenzo
Powered by blists - more mailing lists