From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Pekka Paalanen" <ppaalanen@gmail.com>,
jim.cromie@gmail.com, "Łukasz Bartosik" <lb@semihalf.com>,
linux-kernel@vger.kernel.org,
"wayland-devel@lists.freedesktop.org"
<wayland-devel@lists.freedesktop.org>,
"Sean Paul" <seanpaul@chromium.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v1] dynamic_debug: add support for logs destination
Date: Mon, 16 Oct 2023 11:03:12 -0400 [thread overview]
Message-ID: <20231016110312.3d18ea82@gandalf.local.home> (raw)
In-Reply-To: <ZSfCMBXOOi9Luc6F@phenom.ffwll.local>
On Thu, 12 Oct 2023 11:53:52 +0200
Daniel Vetter <daniel@ffwll.ch> wrote:
> > You said that turning the kernel ring buffer contents into strings is a
> > very heavy operation, so it is not possible to push this scope
> > separation to userspace, right?
>
> I think it's the kernel that does the formatting, but honestly not sure
> how this works with perf traces. Might be that it's actually userspace
> doing the formatting later on so that it doesn't incur the overhead while
> recording.
perf and trace-cmd do the formatting in user space via libtraceevent:
git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git
It reads the format files of the events:
/sys/kernel/tracing/events/*/*/format
and uses that to read the raw data saved from the kernel into human
readable output.
Note, this means that addresses coming from kernel trace events are not
hashed!
-- Steve
next prev parent reply other threads:[~2023-10-16 15:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 15:48 Łukasz Bartosik
2023-09-15 18:02 ` jim.cromie
2023-09-18 7:20 ` Łukasz Bartosik
2023-10-02 10:07 ` Łukasz Bartosik
2023-10-02 20:49 ` jim.cromie
2023-10-03 19:58 ` Steven Rostedt
2023-10-03 20:53 ` jim.cromie
2023-10-04 10:55 ` Łukasz Bartosik
2023-10-05 17:14 ` Łukasz Bartosik
2023-10-06 20:49 ` jim.cromie
2023-10-09 22:47 ` Łukasz Bartosik
2023-10-10 16:01 ` jim.cromie
2023-10-10 16:06 ` jim.cromie
2023-10-11 8:48 ` Pekka Paalanen
2023-10-11 9:42 ` Daniel Vetter
2023-10-11 13:59 ` Łukasz Bartosik
2023-10-12 8:55 ` Pekka Paalanen
2023-10-12 9:53 ` Daniel Vetter
2023-10-12 10:39 ` Pekka Paalanen
2023-10-12 13:18 ` Daniel Vetter
2023-10-16 15:03 ` Steven Rostedt [this message]
2023-10-12 18:48 ` jim.cromie
2023-10-16 15:13 ` Łukasz Bartosik
2023-10-18 3:08 ` jim.cromie
2023-10-19 13:21 ` Łukasz Bartosik
2023-10-11 13:47 ` Łukasz Bartosik
2023-10-24 16:24 ` Jason Baron
2023-10-25 7:58 ` Łukasz Bartosik
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=20231016110312.3d18ea82@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jim.cromie@gmail.com \
--cc=lb@semihalf.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ppaalanen@gmail.com \
--cc=seanpaul@chromium.org \
--cc=wayland-devel@lists.freedesktop.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®