From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: richard clark <richard.xnu.clark@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: About the output interpretation of the wip RV
Date: Tue, 25 Oct 2022 09:16:43 +0200 [thread overview]
Message-ID: <bad5e241-4fc4-df03-894e-3c0a6d0f5ff0@kernel.org> (raw)
In-Reply-To: <CAJNi4rN7WkbEJkr9+vP1bOXQ_U=4eyDSaHb1aqJti_rTs2K7Hw@mail.gmail.com>
Hi Richard!
On 10/25/22 09:10, richard clark wrote:
> Hi Daniel,
> I got several dmsg outputs like this after I insmod the 'wip' into
> system(with printk+dump_stack reactor, trivial changes for the wip):
Which version of the monitor are you using? I make this question because the
latest version of the monitor is not "loadable module" yet. So my guess is that
you are using a version from the paper?
> [78706.972957] event sched_waking not expected in the state preemptive
> [78706.972963] CPU: 2 PID: 410 Comm: kworker/2:4 Tainted: G
> OE 5.15.70-rt50 #1
> [78706.972972] Workqueue: events igb_watchdog_task [igb]
> [78706.973000] Call Trace:
> [78706.973003] <IRQ>
> [78706.973006] dump_stack_lvl+0x61/0x86
> [78706.973016] dump_stack+0x10/0x18
> [78706.973022] handle_sched_wakeup+0x92/0xd0 [rv_poc]
> [78706.973028] ttwu_do_wakeup+0xc3/0x1d0
> [78706.973038] ttwu_do_activate+0x6e/0x100
> [78706.973044] try_to_wake_up+0x209/0x700
> [78706.973049] ? hrtimer_interrupt+0x11f/0x230
> [78706.973059] wake_up_process+0x15/0x30
> [78706.973065] irq_exit_rcu+0x9b/0xe0
> [78706.973074] sysvec_apic_timer_interrupt+0x92/0xd0
> [78706.973082] </IRQ>
> [78706.973083] <TASK>
> [78706.973084] asm_sysvec_apic_timer_interrupt+0x1b/0x20
>
> Does that mean something is not unexpected in the system?
Not necessarily, this monitor shows a limitation of tracing, as explained in
the kernel documentation:
https://docs.kernel.org/trace/rv/monitor_wip.html
Anyway, I suggest you using the upstream version of the monitors...
-- Daniel
> Thanks,
> Richard
next prev parent reply other threads:[~2022-10-25 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 7:10 About the output interpretation of the wip RV richard clark
2022-10-25 7:16 ` Daniel Bristot de Oliveira [this message]
2022-10-25 9:18 ` richard clark
2022-10-26 3:52 ` richard clark
2022-10-28 3:37 ` richard clark
2022-10-28 7:24 ` Daniel Bristot de Oliveira
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=bad5e241-4fc4-df03-894e-3c0a6d0f5ff0@kernel.org \
--to=bristot@kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=richard.xnu.clark@gmail.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;
as well as URLs for NNTP newsgroup(s).