Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp6029283ybi; Wed, 29 May 2019 01:33:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqwTCNTdYA/ZUs1XNk7g/b584lUT229qCxhh0e5rLZ2nSOXpMukE8I32/RM8qy7NxcrCWq93 X-Received: by 2002:a62:798b:: with SMTP id u133mr82590634pfc.210.1559118814398; Wed, 29 May 2019 01:33:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559118814; cv=none; d=google.com; s=arc-20160816; b=esxKLLfkeh4lMfGryFQ2fkBpDtxcpWzuGy8jEf41Bi2pGtsBNEn0WYxcA0sRG2AOB1 siQM3ZHGsStEP5TmoZBzFIlW1qPx3sPeUhf4BnVycOexoWx174fisDl1P/BOvi/1Wo/Q hzVihTX4ZIn722PYtkmPZBlEg7ek6s6WjnplNiEs7Lg+VA8szJyf0T6r0jqNHlkjC5Sm h//BZEYqUjRfMfe9+VQvRptPuNIbgqMkyluqg58sisj2F2QV+n0rILoSeBfJST0Y9u/c jrv7fKVY6rj97TmrtKgbBdnGOdTQMCGHx5lTQ4mLuUnNQ6FoEUh0p+ADJYnry2YkPoy5 NX0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=qHlOuS3EPU1InrStLL0vWRkGRnAkkD7pqVRpdJuJgy8=; b=XFLqS5A/gfbqsOKXBjsTXjzc3a8Cd9UVOspEWK3AkDSrIOxssexpt4O5C+EBsdo9tK oUll8GPlOTK49LvoGkvhM876z4ZH+0wmI90ymuRq7zithgX5LH+msSH5TYxGhTegdvkW AsZpvsuQ4klZheFjnbGXHhryu3MRISE8ryQTf4N1txSX3/5f+Lho/fmfz9F7vLK0Qi3X ko/jAOITVJgEiWPjdMlUzdFZHiT8wu2lLW8gWkvt3iTgr/VpvSogshhxTOshtPtfCqVM m1k0SsXGPG5NkT015b6B0njL7RM5cZ/Wwgb6Fwh/kY8Jt64OYQWF1TjF/nFxSgIIPZtm wcdg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=mso3y4TG; 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 x8si6011575pjq.80.2019.05.29.01.33.17; Wed, 29 May 2019 01:33:34 -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; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=mso3y4TG; 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 S1726738AbfE2Iau (ORCPT + 99 others); Wed, 29 May 2019 04:30:50 -0400 Received: from merlin.infradead.org ([205.233.59.134]:60332 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725911AbfE2Iat (ORCPT ); Wed, 29 May 2019 04:30:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=qHlOuS3EPU1InrStLL0vWRkGRnAkkD7pqVRpdJuJgy8=; b=mso3y4TGmF//O2klOJuNi5Ofd Ae0hezHWGF3Isa/mqDehZennmq4YFa+C9l2QmT7+LM6OxEZLqIcZ7XXY4+XXwN3yW4ev75r/pUQ2d 70WEW8k/NWN+oKT2AtMY4VQH/+0cD2ycbLeCdcJIRotXvkG/fPYrnN+sRnowaFc0KmT0NhPA2ivAf jjKdPideQFk4kJ/doFIzou6ooWrvGNXus3KmmsNX6eI/I96CPtlPAHEtKg3LCEx/BJz4AzI/vOT62 xd/6eyZ8srT4S7rylnlCwOmApXl0ptqq5ykrYZU+tjxNADgj6WX5Oxuk55yRajvOEMvAxnIF9WjNo nCO47x4DQ==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1hVtxy-0002VE-OP; Wed, 29 May 2019 08:29:47 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id 4EE30201A7E41; Wed, 29 May 2019 10:29:45 +0200 (CEST) Date: Wed, 29 May 2019 10:29:45 +0200 From: Peter Zijlstra To: Daniel Bristot de Oliveira Cc: linux-kernel@vger.kernel.org, williams@redhat.com, daniel@bristot.me, "Steven Rostedt (VMware)" , Ingo Molnar , Thomas Gleixner , "Paul E. McKenney" , Matthias Kaehlcke , "Joel Fernandes (Google)" , Frederic Weisbecker , Yangtao Li , Tommaso Cucinotta Subject: Re: [RFC 1/3] softirq: Use preempt_latency_stop/start to trace preemption Message-ID: <20190529082945.GE2623@hirez.programming.kicks-ass.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 28, 2019 at 05:16:22PM +0200, Daniel Bristot de Oliveira wrote: > prempt_disable/enable tracepoints occurs only in the preemption > enabled <-> disable transition. As preempt_latency_stop() and > preempt_latency_start() already do this control, avoid code > duplication by using these functions in the softirq code as well. > > RFC: Should we move preempt_latency_start/preempt_latency_stop > to a trace source file... or even a header? Yeah, a header might not be a bad idea. > @@ -130,12 +132,8 @@ void __local_bh_disable_ip(unsigned long ip, unsigned int cnt) > trace_softirqs_off(ip); > raw_local_irq_restore(flags); > > - if (preempt_count() == cnt) { > -#ifdef CONFIG_DEBUG_PREEMPT > - current->preempt_disable_ip = get_lock_parent_ip(); > -#endif > - trace_preempt_off(CALLER_ADDR0, get_lock_parent_ip()); > - } > + preempt_latency_start(cnt); > + I'm thinking we can do without that empty line. > } > EXPORT_SYMBOL(__local_bh_disable_ip); > #endif /* CONFIG_TRACE_IRQFLAGS */