Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp4633558pxb; Thu, 14 Oct 2021 08:58:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxP9nt+uMzx89crRgem1KsqJ+D0iFjnDyJ7VcOKPkgahpndRIP2UGPzwflO+B4PAt/eMtPj X-Received: by 2002:a17:907:8a12:: with SMTP id sc18mr4502252ejc.569.1634227108047; Thu, 14 Oct 2021 08:58:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634227108; cv=none; d=google.com; s=arc-20160816; b=ycvL0i5jso3yBNV8dXphgkw++YQwUETuDMiB1xXWM2Yn5IklM2NHsavKZwKheNth62 om9cU8i/ZfvMrHp3ZssVn0/5d7UOAdpz1OHLBAlPbS4GQgwsscKht2e6LaiNIBE4hP+r 6k6PKLYxBuocPBZyTD5D/v0m5kGegZT4wwADsqKQr87sLKvK6/qmfsh6HHaqbfD3J09R 8Sy7WXaDGkflWSH6pRE55Lg0gw3jvlKFULTPWsL4+92T5t5E12z+gqapaJkpxfmQOPKx 9QF2up5QdEniWIEKbX66TSt2wrNRsiE4h2KNTNttcfTDGsOdXPNoax3VUXo2EwyQbHxz y6Lw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=lpsyVGbznXia4ZeteMKtreBapaSS4+qtDh15KfP1wSA=; b=m9qHO7Ku7OFUAWAyAdhWJ1Dp3Yb2Y373nxfRcrtgQIv162qCJuzK5DKUnpiJhb5co0 N4pDZb0b7XtrvsbxVNvhSbAF2yKR8IphvWl0vuuBlaWWyd5//vTwqfwqXEwbLd5xe7Sn E23bOPeftxmqZh+PhuEXFn+ry6DuXp8HUbRdZevQvhrpmwatAcya5l5y/2pkVr3TX4zu GiEC/+5lOmU47/gzEswIa1ff1vh3bFNurR1Rc4nVGgYkSs1LkJUveR+jcdmV3qi8/BBa 7TT6ukky4hRQuf/lh4175Vf7LxpwuMfavjYaXh8UnQbE/As0l48HWyeZlDZgLph19sOO FDXA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p28si3573723edi.290.2021.10.14.08.58.04; Thu, 14 Oct 2021 08:58:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231767AbhJNOuV (ORCPT + 99 others); Thu, 14 Oct 2021 10:50:21 -0400 Received: from mail.kernel.org ([198.145.29.99]:39100 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231396AbhJNOuU (ORCPT ); Thu, 14 Oct 2021 10:50:20 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5FB0660EE2; Thu, 14 Oct 2021 14:48:13 +0000 (UTC) Date: Thu, 14 Oct 2021 10:48:11 -0400 From: Steven Rostedt To: Yafang Shao Cc: Mathieu Desnoyers , acme , kernel test robot , 0day robot , Petr Mladek , Kees Cook , Peter Zijlstra , Alexander Viro , linux-kernel , lkp , Andrew Morton , Valentin Schneider , Qiang Zhang , robdclark , christian , Dietmar Eggemann , Ingo Molnar , Juri Lelli , Vincent Guittot , Ben Segall , Mel Gorman , bristot , aubrey li , yu c chen Subject: Re: [sched.h] 317419b91e: perf-sanity-tests.Parse_sched_tracepoints_fields.fail Message-ID: <20211014104811.356e11ae@gandalf.local.home> In-Reply-To: References: <20211010102429.99577-4-laoar.shao@gmail.com> <20211014072707.GA18719@xsang-OptiPlex-9020> <1529739526.13983.1634215325995.JavaMail.zimbra@efficios.com> <173454728.14036.1634216949862.JavaMail.zimbra@efficios.com> <1171592945.14099.1634219447199.JavaMail.zimbra@efficios.com> X-Mailer: Claws Mail 3.17.8 (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, 14 Oct 2021 22:40:04 +0800 Yafang Shao wrote: > > mount -t tracefs nodev /sys/kernel/tracing > > cat /sys/kernel/tracing/events/sched/sched_switch/format > > > > name: sched_switch > > ID: 314 > > format: > > [...] > > field:char prev_comm[16]; offset:8; size:16; signed:1; > > [...] > > field:char next_comm[16]; offset:40; size:16; signed:1; > > > > Both of those fields expose a fixed-size of 16 bytes. > > > > AFAIK Steven's intent was that by parsing this file, trace viewers could adapt to > > changes in the event field layout. Unfortunately, there have been cases where > > trace viewers had a hard expectation on the field layout. Hopefully those have > > all been fixed a while ago. > > > > I don't have a clear idea what will happen to trace viewers if we > extend task comm. There shouldn't be any doing a hard coded read of the events. That happened once with powertop, but they broke when they ran 32 bit userspace on a 64 bit kernel, and they switched to libtraceevent to fix it. Which handles these updates. > > Steven, do you have any suggestions ? The "Don't break user space" is a "tree in the forest" argument. We break user space all the time. But if no user space tool is around to hear it, did it really break? The answer is "no". -- Steve