From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 05CEECDB465 for ; Mon, 16 Oct 2023 15:01:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233844AbjJPPBt (ORCPT ); Mon, 16 Oct 2023 11:01:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36724 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233263AbjJPPBo (ORCPT ); Mon, 16 Oct 2023 11:01:44 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 409C5E6 for ; Mon, 16 Oct 2023 08:01:39 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0EA23C433C8; Mon, 16 Oct 2023 15:01:37 +0000 (UTC) Date: Mon, 16 Oct 2023 11:03:12 -0400 From: Steven Rostedt To: Daniel Vetter Cc: Pekka Paalanen , jim.cromie@gmail.com, =?UTF-8?B?xYF1a2Fzeg==?= Bartosik , linux-kernel@vger.kernel.org, "wayland-devel@lists.freedesktop.org" , Sean Paul , dri-devel Subject: Re: [PATCH v1] dynamic_debug: add support for logs destination Message-ID: <20231016110312.3d18ea82@gandalf.local.home> In-Reply-To: References: <20231003155810.6df9de16@gandalf.local.home> <20231011114816.19d79f43@eldfell> <20231012115548.292fa0bb@eldfell> X-Mailer: Claws Mail 3.19.1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 12 Oct 2023 11:53:52 +0200 Daniel Vetter 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