From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: "Chen, Zide" <zide.chen@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@redhat.com>,
Yi Lai <yi1.lai@linux.intel.com>
Subject: Re: [PATCH v3] perf: map pages in advance
Date: Fri, 20 Dec 2024 09:31:07 +0000 [thread overview]
Message-ID: <4ded2d63-03dd-498e-9810-690a9eff0c22@lucifer.local> (raw)
In-Reply-To: <65a04f0d-668b-47b6-a532-d1e11ef4835a@intel.com>
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
next prev parent reply other threads:[~2024-12-20 9:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 8:29 Lorenzo Stoakes
2024-12-19 21:17 ` Chen, Zide
2024-12-20 9:31 ` Lorenzo Stoakes [this message]
2024-12-20 9:56 ` David Hildenbrand
2024-12-20 19:36 ` Chen, Zide
2024-12-20 21:29 ` David Hildenbrand
2024-12-20 21:53 ` David Hildenbrand
2024-12-23 11:10 ` Lorenzo Stoakes
2024-12-23 21:12 ` David Hildenbrand
2025-01-03 14:45 ` Lorenzo Stoakes
2025-01-03 20:36 ` Chen, Zide
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=4ded2d63-03dd-498e-9810-690a9eff0c22@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=david@redhat.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=willy@infradead.org \
--cc=yi1.lai@linux.intel.com \
--cc=zide.chen@intel.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