Linux Perf Users
 help / color / mirror / Atom feed
From: Veronika Molnarova <vmolnaro@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	Michael Petlan <mpetlan@redhat.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf kmem --page stat and gpf_flags translation
Date: Fri, 22 Nov 2024 13:53:19 +0100	[thread overview]
Message-ID: <2f3c92d9-a9b0-45be-a416-3c6b5ecf8710@redhat.com> (raw)
In-Reply-To: <20241121100326.645bd0d7@gandalf.local.home>

[-- Attachment #1: Type: text/plain, Size: 2114 bytes --]



On 11/21/24 16:03, Steven Rostedt wrote:
> On Thu, 21 Nov 2024 14:54:25 +0100 (CET)
> Michael Petlan <mpetlan@redhat.com> wrote:
> 
>> Hello Steve and others,
>>
>> We have found out that perf kmem --page stat sometimes fails like the
>> following:
>>
>> # perf kmem --page stat
>> 0x2aa28 [0x8]: failed to process type: 68 [Operation not permitted]
>> error during process events: -1
>>
>> This seem to happen on s390x KVM machines.
>>
>> When we tried to investigate for the reasons, it seems that the problem
>> is caused by incorrect/unexpected translation of gpf_flags for event
>> kmem:mm_page_alloc.
>>
>> # perf script
>> perf   96553 [003] 100299.663963: kmem:mm_page_alloc: page=0x1a8f9 pfn=0x1a8f9 order=0 migratetype=0 gfp_flags=0x500cc2
>> perf   96553 [003] 100299.663995: kmem:mm_page_alloc: page=0x1bc3f pfn=0x1bc3f order=0 migratetype=0 gfp_flags=0x40cc0
>> perf   96553 [003] 100299.664001: kmem:mm_page_alloc: page=0x1a9d9 pfn=0x1a9d9 order=0 migratetype=0 gfp_flags=0x40cc0
>> perf   96553 [003] 100299.664011: kmem:mm_page_alloc: page=0x1788b pfn=0x1788b order=0 migratetype=0 gfp_flags=0x40cc0
>> perf   96553 [003] 100299.664023: kmem:mm_page_alloc: page=0x17993 pfn=0x17993 order=0 migratetype=0 gfp_flags=0xcc0
>>
> 
> Does the same thing happen with trace-cmd record?
> 
>  # trace-cmd record -e mm_page_alloc
> [ run tests, hit Ctrl^C ]
> 
>  # trace-cmd report
> 
> ?
The trace-cmd report is the same it seems:

    perf-217873 [001] 348026.665461: mm_page_alloc:        page=0x31524d936cd pfn=0x824f5 order=0 migratetype=0 gfp_flags=0x500cc2
    perf-217873 [001] 348026.665471: mm_page_alloc:        page=0x31524e9d49a pfn=0x18c2c2 order=0 migratetype=1 gfp_flags=0x140cca
    perf-217873 [001] 348026.665474: mm_page_alloc:        page=0x31524ea8565 pfn=0x19738d order=0 migratetype=1 gfp_flags=0x140cca
    perf-217873 [001] 348026.665477: mm_page_alloc:        page=0x31524db8925 pfn=0xa774d order=0 migratetype=1 gfp_flags=0x140cca

Sending the trace.dat file as an attachment.

Thanks,
Veronika
> 
> If so, could you send the trace.dat file to me.
> 
> Thanks,
> 
> -- Steve
> 

[-- Attachment #2: trace.dat --]
[-- Type: application/octet-stream, Size: 1124903 bytes --]

  reply	other threads:[~2024-11-22 12:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 13:54 perf kmem --page stat and gpf_flags translation Michael Petlan
2024-11-21 15:03 ` Steven Rostedt
2024-11-22 12:53   ` Veronika Molnarova [this message]
2025-01-16 14:34   ` Veronika Molnarova
2025-01-16 16:47     ` Steven Rostedt

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=2f3c92d9-a9b0-45be-a416-3c6b5ecf8710@redhat.com \
    --to=vmolnaro@redhat.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=rostedt@goodmis.org \
    /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