linux-kernel - Re: [PATCH v3] perf: map pages in advance

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <860a1ef0-678d-414d-8511-9695b90c3ca0@redhat.com>
Date: Fri, 20 Dec 2024 10:56:50 +0100
From: David Hildenbrand <david@...hat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
 "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>, Yi Lai <yi1.lai@...ux.intel.com>
Subject: Re: [PATCH v3] perf: map pages in advance

On 20.12.24 10:31, Lorenzo Stoakes wrote:
> 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).

Zide Chen, can you try with and without this patch to see if it 
introduces the issue?

-- 
Cheers,

David / dhildenb