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;
Date:   Wed, 20 May 2020 15:33:50 +0200
From:   Peter Zijlstra <peterz@infradead.org>
To:     Wojciech Kudla <wk.kernel@gmail.com>
Cc:     linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
        Nadav Amit <namit@vmware.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] smp: generic ipi_raise tracepoint
Message-ID: <20200520133350.GN317569@hirez.programming.kicks-ass.net>
References: <02b57f31-fc0c-df35-57bf-e0a297a7e6c4@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <02b57f31-fc0c-df35-57bf-e0a297a7e6c4@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Wed, May 20, 2020 at 02:17:21PM +0100, Wojciech Kudla wrote:
> Preliminary discussion: https://lkml.org/lkml/2020/5/13/1327

We have bright shiny links like: https://lkml.kernel.org/r/$MSG-ID for
that. they allow me to go find the email in my local archive without
having to use a browser.

> This patch avoids introducing arch-specific trace points by leveraging
> existing definition for ipi_raise.


> +static const char *ipi_reason_missing __tracepoint_string = "";

That is a pretty crap reason ;-)