From mboxrd@z Thu Jan 1 00:00:00 1970 From: Valentin Schneider Subject: Re: [RFC PATCH 0/5] Generic IPI sending tracepoint Date: Tue, 11 Oct 2022 17:40:26 +0100 Message-ID: References: <20221007154145.1877054-1-vschneid@redhat.com> <3e680bb9-9896-3665-dd59-4f2e6f8205bb@redhat.com> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665506430; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3pR097ooCx/8nlTemhEf/WDhel/4mmcsp3Jh/tnUV8M=; b=A+FV3O0WHCmo+SwD1nwchs7jR+YgzkGCAwje9Xx3LqMKaKhNYS22PO9aAlAwPJn07I5J2/ kpV/PO/oqIwdn/6o7zffLkdhZI0qNV9qD7Fex2Kug3yazce+8QPRClHb1QT7y44M5ZDAjI W5+8s3e6cgGXu8OzkGbgwLWyS5n4UjQ= In-Reply-To: <3e680bb9-9896-3665-dd59-4f2e6f8205bb@redhat.com> List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Daniel Bristot de Oliveira Cc: linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org, linux-snps-arc@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, loongarch@lists.linux.dev, linux-mips@vger.kernel.org, openrisc@lists.librecores.org, linux-parisc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-xtensa@linux-xtensa.org, x86@kernel.org, "Paul E. McKenney" , Steven Rostedt , Peter Zijlstra , Thomas Gleixner , Sebastian Andrzej Siewior , Juri Lelli , Fred On 11/10/22 18:22, Daniel Bristot de Oliveira wrote: > On 10/11/22 18:17, Valentin Schneider wrote: >> Thinking out loud, it makes way more sense to record a cpumask in the >> tracepoint, but perhaps we could have a postprocessing step to transform >> those into N events each targeting a single CPU? > > My approach on the tracers/rtla is to make the simple things in kernel, and beautify > things in user-space. > > You could keep the tracepoint as a mask, and then make it pretty, like cpus=3-5,8 > in user-space. For example with a trace-cmd/perf loadable plugin, libtracefs helper. > That's a nice idea, the one downside I see is that means registering an event handler for all events with cpumasks rather than directly targeting cpumask fields, but that doesn't look too horrible. I'll dig a bit in that direction. > For rtla I was thinking to make a new tool to parse them. and make it pretty there. > > -- Daniel