Received: by 2002:a25:e7d8:0:0:0:0:0 with SMTP id e207csp1899048ybh; Sun, 8 Mar 2020 16:26:56 -0700 (PDT) X-Google-Smtp-Source: ADFU+vv7GSs+wraSsPBXmPlm4G0buWb2rOVporzv61PVCzutXabuiHuN7JkEBqZxbyXwHq7X2t2F X-Received: by 2002:a9d:6d96:: with SMTP id x22mr11207093otp.264.1583710016775; Sun, 08 Mar 2020 16:26:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1583710016; cv=none; d=google.com; s=arc-20160816; b=WeybbxrsqdmvDMG2GHi6hbJMCsfjW4jG1r+pxDcdLOLtr6RtAT2/Ji3Jmq5VXDMUyY Wk+QRKzAnhs3ClOIm6JrCXzJshVDh2jMhmGSMVF6YSCtDt2Il14ZbIl/vPFDIEm+96qg vCcqsPD4D44x9r3Adb8hGq1QGGA/V/EgGKgDC3mPbQPttOEWsqIhBlRJci4Nzci09KNU YzNuUeHfyv+ytZi2dxBB5s6efhhNg1CpTpcooYiEirFEzpwyfhhg8i5hYSp7SqOQcHs1 ZYdZ0VScG9F023omOMnm6yXczLJkF8Df81ezfcO37CXQouy7rG3fvkJ+vvitn/aUkdcy YnmQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:subject:cc:to :from:date:user-agent:message-id; bh=ZiVE+Q2XWodYiUEfqeL7Vhhgett7hEnKMgKjgxvJ/38=; b=DFFvKVAqGZ58M2FH9RmewM9bte9j5YZEZ+GaFpJsOXh7tibEX3SK+ksbWX3QKhppkC QgRpFCTWf8kESaOOzQJWGzDMdfuaDpz8DohJuTYWLIpFxuXan95RPdcydZmfxFsydCSf t1P90bGKLb88X+xmXvrW7BZ/lj09LrXP4a7hi8JwIU7ciEjcRD0uPVdF6et4G5heJDnv bSuqV/qKCZJlkKAnQXd83NoNWNHSkdV/wotVgCE16Rulg42GVQZr1xoOFjBtVBlEq9QU qPgCVy2cPwxAFgTHBE4W6JnMyhaeJLy5PdIWa8zZs11kyNUv224VzcDuXez6vcrktYpk h5/A== 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 s4si5346503otd.37.2020.03.08.16.26.45; Sun, 08 Mar 2020 16:26:56 -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 S1727334AbgCHXZo (ORCPT + 99 others); Sun, 8 Mar 2020 19:25:44 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:57239 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726668AbgCHXXz (ORCPT ); Sun, 8 Mar 2020 19:23:55 -0400 Received: from p5de0bf0b.dip0.t-ipconnect.de ([93.224.191.11] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1jB5Gg-00035I-LO; Mon, 09 Mar 2020 00:23:35 +0100 Received: from nanos.tec.linutronix.de (localhost [IPv6:::1]) by nanos.tec.linutronix.de (Postfix) with ESMTP id 05C631040AD; Mon, 9 Mar 2020 00:23:30 +0100 (CET) Message-Id: <20200308222609.825111830@linutronix.de> User-Agent: quilt/0.65 Date: Sun, 08 Mar 2020 23:24:08 +0100 From: Thomas Gleixner To: LKML Cc: x86@kernel.org, Steven Rostedt , Brian Gerst , Juergen Gross , Frederic Weisbecker , Alexandre Chartre Subject: [patch part-II V2 09/13] x86/entry/common: Split hardirq tracing into lockdep and ftrace parts References: <20200308222359.370649591@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org trace_hardirqs_off() is in fact a tracepoint which can be utilized by BPF, which is unsafe before calling enter_from_user_mode(), which in turn invokes context tracking. trace_hardirqs_off() also invokes lockdep_hardirqs_off() under the hood. OTOH lockdep needs to know about the interrupts disabled state before enter_from_user_mode(). lockdep_hardirqs_off() is safe to call at this point. Split it so lockdep knows about the state and invoke the tracepoint after the context is set straight. Even if the functions attached to a tracepoint would all be safe to be called in rcuidle having it split up is still giving a performance advantage because rcu_read_lock_sched() is avoiding the whole dance of: scru_read_lock(); rcu_irq_enter_irqson(); ... rcu_irq_exit_irqson(); scru_read_unlock(); around the tracepoint function invocation just to have the C entry points of syscalls call enter_from_user_mode() right after the above dance. Signed-off-by: Thomas Gleixner --- V2: New patch --- arch/x86/entry/common.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) --- a/arch/x86/entry/common.c +++ b/arch/x86/entry/common.c @@ -60,10 +60,19 @@ static __always_inline void syscall_entr { /* * Usermode is traced as interrupts enabled, but the syscall entry - * mechanisms disable interrupts. Tell the tracer. + * mechanisms disable interrupts. Tell lockdep before calling + * enter_from_user_mode(). This is safe vs. RCU while the + * tracepoint is not. */ - trace_hardirqs_off(); + lockdep_hardirqs_on(CALLER_ADDR0); + enter_from_user_mode(); + + /* + * Tell the tracer about the irq state as well before enabling + * interrupts. + */ + __trace_hardirqs_off(); local_irq_enable(); }