mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Veronika Molnarova <vmolnaro@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Michael Petlan <mpetlan@redhat.com>
Subject: Re: [PATCH] perf test: Fix probe testsuite with a new error message
Date: Thu, 10 Oct 2024 15:30:57 +0200	[thread overview]
Message-ID: <af8c186d-72ba-4fcb-8737-84b665017cdd@redhat.com> (raw)
In-Reply-To: <ZwfNmDNzQAXf0ZQV@x1>



On 10/10/24 14:50, Arnaldo Carvalho de Melo wrote:
> On Thu, Oct 10, 2024 at 09:48:52AM -0300, Arnaldo Carvalho de Melo wrote:
>> On Wed, Oct 09, 2024 at 10:16:20PM -0700, Namhyung Kim wrote:
>>> On my system, it's constantly failing because of new error message from
>>> perf probe.  It should update the regex pattern to match the message -
>>> "A function DIE doesn't have decl_line. Maybe broken DWARF?".
>>>
>>>   $ sudo head -n 2 /sys/kernel/debug/kprobes/blacklist | cut -f2
>>>   warn_thunk_thunk
>>>   asm_exc_divide_error
>>>
>>>   $ sudo perf probe warn_thunk_thunk
>>>   A function DIE doesn't have decl_line. Maybe broken DWARF?
>>>   A function DIE doesn't have decl_line. Maybe broken DWARF?
>>>   Probe point 'warn_thunk_thunk' not found.
>>>     Error: Failed to add events.
>>>
>>>   $ sudo perf probe asm_exc_overflow
>>>   Failed to find scope of probe point.
>>>     Error: Failed to add events.
>>
>> We discussed this in the past, I came up with a similar patch, Veronika
>> rightly pointed out that this may point to a real problem, Masami said
>> that since these are for DWARF from assembly those are known issues, I
>> suggested Veronika checked if the CU where the function came from was
>> generated from Assembly (there are DWARF tags that have that info), IIRC
>> she said she would try to do it.
>>
>> I'll try to find out the threads and see what happened.
> 
> https://lore.kernel.org/all/ZvXhJLkJcR99Y2sF@google.com/T/#u
> 
> Veronika, was there a v3?
> 
> Thanks,
Well the patch was already applied upstream so we are talking about a fix
not v3, right? As Arnaldo mentioned, I got together a fix patch that checks
the CU for the Assembly for blacklisted probe. Michael also suggested the 
possibility to check multiple blacklisted probes if we are not able to check
for the Assembly, so I also added that.

I will send the fix patch soon as part of the perftool upstreaming patchset
to prevent conflicts happening. Hopefully, this can be at the start of the
next week if all of the checks pass.

Thanks,
Veronika
> 
> - Arnaldo
> 


  reply	other threads:[~2024-10-10 13:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10  5:16 Namhyung Kim
2024-10-10 12:48 ` Arnaldo Carvalho de Melo
2024-10-10 12:50   ` Arnaldo Carvalho de Melo
2024-10-10 13:30     ` Veronika Molnarova [this message]
     [not found]       ` <CA+JHD91skZHrEanhANQzWaq=4wpZomTn8Vab4j+wT2kHdibTkA@mail.gmail.com>
2024-10-15 10:46         ` Veronika Molnarova
2024-10-16  1:57           ` Namhyung Kim
2024-10-11  0:06   ` Namhyung Kim

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=af8c186d-72ba-4fcb-8737-84b665017cdd@redhat.com \
    --to=vmolnaro@redhat.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®