Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp101498ybg; Tue, 22 Oct 2019 16:55:15 -0700 (PDT) X-Google-Smtp-Source: APXvYqzytBPrWrw/It2t1MFeVk3z85pId+F6RS95i5q3kaUm+LhD48FIuzQq1fKRuKfj0TcJRpOF X-Received: by 2002:a05:6402:1b1a:: with SMTP id by26mr9079258edb.178.1571788515210; Tue, 22 Oct 2019 16:55:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571788515; cv=none; d=google.com; s=arc-20160816; b=ZXMHVSSjNL3sHLxgThhWNAd+Kvf1VO855JBIBRy6nZnkKTc+2Ax6BS1ULoMUiNEE7x OAyuN/JwZEnW57clfJHcWKKjF2SSr36pRBA/J3X25KAhONpESkX98Px0S5e8YMyA5gtc Xk4i0Ew4aSgKUKtxskR0UeWPnN8I48hfNGhECveiQHeIKvB+XptFoHfBGiR6zk00UVVn 7UU7sCURsyiK/B9SEc8NwgZUnfi3u1bFKbggd40uaYYdhDV0z23WxfcJ97f8I9StsnLD QRBDXcImoG4RMjeIzCcoMBfUvg9rnVUoHgQRUvzPJa7PUhly5kvc+OP++12Adx6/kaA5 IX5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=kWQ3CHqz+qwwTUU0DcntRviyxpqgFYZaQnqRiI9oCiQ=; b=tSTvuxjTCJva2z1GO/s88nA7rFxZG3DkD9fBvrtacbtg16wP2l6Dymx8VrVXEr48PJ 0j7fWeQ4YUy24bm1JpLMYxL55HNncgWp7bfdPPMbbrbDNp+reOqNnBX922dBkWyvPMXc jDzigNejrtseEhaI2JrgFInZejYzoDlrh11azDlxnVGZpLejQVcXF3jDyzXlGOwdGp49 W8W7gm6Jfc466e1OTK4/izESCtbXObSbDUJ4kJ4kw6SYWuSYqXvEYSlR01oCV/+MHIQI gLMq3jHykiedQymallPSvc15Bm0dUf4rWNPHXwcO5iWSzCSYZXXxk6Hf33z4PWUzHkJ8 egtg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p29si227139eda.104.2019.10.22.16.54.51; Tue, 22 Oct 2019 16:55:15 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732071AbfJVUk0 (ORCPT + 99 others); Tue, 22 Oct 2019 16:40:26 -0400 Received: from mail.kernel.org ([198.145.29.99]:33800 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727582AbfJVUk0 (ORCPT ); Tue, 22 Oct 2019 16:40:26 -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 A9CCC21848; Tue, 22 Oct 2019 20:40:24 +0000 (UTC) Date: Tue, 22 Oct 2019 16:40:23 -0400 From: Steven Rostedt To: Peter Zijlstra Cc: x86@kernel.org, linux-kernel@vger.kernel.org, mhiramat@kernel.org, bristot@redhat.com, jbaron@akamai.com, torvalds@linux-foundation.org, tglx@linutronix.de, mingo@kernel.org, namit@vmware.com, hpa@zytor.com, luto@kernel.org, ard.biesheuvel@linaro.org, jpoimboe@redhat.com, jeyu@kernel.org Subject: Re: [PATCH v4 15/16] module: Move where we mark modules RO,X Message-ID: <20191022164023.2102fb1a@gandalf.local.home> In-Reply-To: <20191022202401.GO1817@hirez.programming.kicks-ass.net> References: <20191018073525.768931536@infradead.org> <20191018074634.801435443@infradead.org> <20191021222110.49044eb5@oasis.local.home> <20191022202401.GO1817@hirez.programming.kicks-ass.net> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 22 Oct 2019 22:24:01 +0200 Peter Zijlstra wrote: > The below seems to cure it; and seems to generate identical > events/*/format output (for my .config, with the exception of ID). > > It has just one section mismatch report that I'm too tired to look at > just now. Thanks, I'll try to take a look at it tomorrow. > > I'm not particularly proud of the "__function__" hack, but it works :/ I If anything, that should be defined as a macro: #define TRACE_EVENT_FIELD_SPECIAL "__trace_event_special__" And use that to test? > couldn't come up with anything else for [uk]probes which seem to have > dynamic fields and if we're having it then syscall_enter can also make > use of it, the syscall_metadata crud was going to be ugly otherwise. > > (also, win on LOC) I'm more worried about text/data bloat. But if anything, we may be able to deal with that later. -- Steve