Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp1475775ybf; Sun, 1 Mar 2020 10:21:05 -0800 (PST) X-Google-Smtp-Source: APXvYqzYHbblBGOM7OHXsxqh1rreIHH3Ps5CZeG9PtBLhV9lqxbf2n/fsy1z9NUWcWM1I7lFzdpy X-Received: by 2002:a05:6830:1098:: with SMTP id y24mr10865112oto.197.1583086864940; Sun, 01 Mar 2020 10:21:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583086864; cv=none; d=google.com; s=arc-20160816; b=LDYKD/MM2u2MX4EujLM21F2TAgf8Ud0P9mlGKjWXAIrqwCyxeeU9ACKM1udK33zM8u yMSv76GvU1Hug/si3wu9DBbNSLJ6XZzZHYmCNkqh4umlZlXdib5FySXyu3iw8YHcr0Ju EKUjYmT01Ij+rs0XHKsc2b1X44cAqTWPKp57kxsDu5fqvAsD3cFWbpmae9ooTPD27zli haxcLRmYlx83sETk1/y1HkoNay7nzm6/N265XCzRDFI2MtS6P6nvMiAW9glxBfUg8NZr oqKX1SsNZDxvI7zmhLJfyMr3hbxkDwL6jIVLejgBhCbMkuFChAJgtYVO3/0bCbGrkmKh YS+Q== 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=gfS0K21ET7wHA5fI/CBI6+fmA/wnh2+8OGEcLfw5+7U=; b=WJwTddgKfVmHNOw04aZLE7Okth1nQ9a3ps/bhvy9tjs+g6tpZUVC6sQymjqjGkBm69 Pbi2CNX7g5uR3frz6WlMdCAscR3EB5dLEBmzgtPDw9LxX+IVtjLSp9b7RIU510gWQeVp GbwIduFLXwqnDSbNHV31uFbxlMbk4/VRK2dlYelSS9jYIau/o5ja8Cj4/7di7v2SAgzL pfeTQarYnm0yUxPh8+MaSA9dwr7/CXynHd01hp+Rw8reTmm0OUwKRTi/a2pHEmzBliAv ntYpQrtwqOurjJO5vgJCD1ggIFLt30/jvYqtQbV4TIghm8p6c70y7fOoWKlpFti1HBh9 O0uA== 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 i2si4618843otc.130.2020.03.01.10.20.51; Sun, 01 Mar 2020 10:21:04 -0800 (PST) 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 S1726603AbgCASUm (ORCPT + 99 others); Sun, 1 Mar 2020 13:20:42 -0500 Received: from mail.kernel.org ([198.145.29.99]:34704 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726448AbgCASUl (ORCPT ); Sun, 1 Mar 2020 13:20:41 -0500 Received: from oasis.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 30B77246CD; Sun, 1 Mar 2020 18:20:40 +0000 (UTC) Date: Sun, 1 Mar 2020 13:20:38 -0500 From: Steven Rostedt To: Thomas Gleixner Cc: Andy Lutomirski , Peter Zijlstra , Andy Lutomirski , LKML , x86@kernel.org, Brian Gerst , Juergen Gross , Paolo Bonzini , Arnd Bergmann , "Paul E. McKenney" , Joel Fernandes Subject: Re: [patch 4/8] x86/entry: Move irq tracing on syscall entry to C-code Message-ID: <20200301132038.7f0def72@oasis.local.home> In-Reply-To: <87d09wf6dw.fsf@nanos.tec.linutronix.de> References: <87imjofkhx.fsf@nanos.tec.linutronix.de> <87d09wf6dw.fsf@nanos.tec.linutronix.de> 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 Sun, 01 Mar 2020 16:21:15 +0100 Thomas Gleixner wrote: > Andy Lutomirski writes: > >> On Mar 1, 2020, at 2:16 AM, Thomas Gleixner wrote: > >> Ok, but for the time being anything before/after CONTEXT_KERNEL is unsafe > >> except trace_hardirq_off/on() as those trace functions do not allow to > >> attach anything AFAICT. > > > > Can you point to whatever makes those particular functions special? I > > failed to follow the macro maze. > > Those are not tracepoints and not going through the macro maze. See > kernel/trace/trace_preemptirq.c For the latency tracing, they do call into the tracing infrastructure, not just lockdep. And Joel Fernandez did try to make these into trace events as well. -- Steve