Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp2353746ybp; Thu, 10 Oct 2019 06:16:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqzpIGRoO3Lnb0BSprrZfTQ//GRtlvqt8VBLnt9Wctm1s+9pNJvTqa7vzKJAihBOMkuESu4V X-Received: by 2002:a05:6402:2025:: with SMTP id ay5mr8077292edb.93.1570713415225; Thu, 10 Oct 2019 06:16:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570713415; cv=none; d=google.com; s=arc-20160816; b=WKnqqn6Lo/f71E59IsCJI+HYb6nInlAQVAqdHBpyXqjmgac2VEnJKTzECkyLnRG8YY RFfH09Y36XuauD9hNtrA2Cr81AxTphhzXy3fSFAzMynF5N/emOKR37biEwxgtTvQ+psc zb+6xF/TY4QYnX5LVIEFKCMo3ZGJMl0givibYrx967G/9iAbbyjIADwD3/UkNPHsWfEl H2e0gtH8qVt86GWEwE9y9ttJbnRulfRSUDFHH4U5cKCFK9LeSCvzHmTHvygNdEe8ogum Y8HxwgXlkLIiDShhrfErhJa37BwobegLJ4iMrCS2wYXkB7WV8OZERPhbVNUo2SHqKDjN yepA== 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=eyJ2zZsrCKjXAV6gsOWzzl8rebyYJi289YmOdlJSPbs=; b=JO1aQTJh/8y0JJqvq7QdSzhjICF5E80s/AfHM+iPUoKwPhhjTaXVXFpO7tseB8prIB m1CMvyIAil6Ywim+TEgLlSxsH5FZQ8Nfm/UHGcT8BwMztAJrHigWddOC64T/bP3TnLxt b5SKCFdIMDXDbjx+2YhYPOgBRUnc/SlJYCe2BrPL/sHwsV2KoUZPvUfvusVsk98bB7N/ WO7DmCCFMtlkHQGfdQo4frO2aX76PxjAzZCu6yB5PZsOdRMgCzP4wQCSLtj1ALei67hz DyWPDauVCcCEGkhQJKf79EfWPnE+vydTPWkTpZ2kAZMm+soVQc9cyxgMal1EFCK/ldid QGqg== 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 c21si3043727ejs.390.2019.10.10.06.16.30; Thu, 10 Oct 2019 06:16:55 -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 S2387790AbfJJNOG (ORCPT + 99 others); Thu, 10 Oct 2019 09:14:06 -0400 Received: from mail.kernel.org ([198.145.29.99]:55932 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727788AbfJJNOG (ORCPT ); Thu, 10 Oct 2019 09:14:06 -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 07647206A1; Thu, 10 Oct 2019 13:14:04 +0000 (UTC) Date: Thu, 10 Oct 2019 09:14:03 -0400 From: Steven Rostedt To: Petr Mladek Cc: jikos@kernel.org, Joe Lawrence , jpoimboe@redhat.com, mingo@redhat.com, Miroslav Benes , linux-kernel@vger.kernel.org, live-patching@vger.kernel.org Subject: Re: [PATCH 0/3] ftrace: Introduce PERMANENT ftrace_ops flag Message-ID: <20191010091403.5ecf0fdb@gandalf.local.home> In-Reply-To: <20191010085035.emsdks6xecazqc6k@pathway.suse.cz> References: <20191007081714.20259-1-mbenes@suse.cz> <20191008193534.GA16675@redhat.com> <20191009112234.bi7lvp4pvmna26vz@pathway.suse.cz> <20191009102654.501ad7c3@gandalf.local.home> <20191010085035.emsdks6xecazqc6k@pathway.suse.cz> 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 Thu, 10 Oct 2019 10:50:35 +0200 Petr Mladek wrote: > It will make the flag unusable for other ftrace users. But it > will be already be the case when it can't be disabled. Honestly, I hate that flag. Most people don't even know about it. It was added in the beginning of ftrace as a way to stop function tracing in the latency tracer. But that use case has been obsoleted by 328df4759c03e ("tracing: Add function-trace option to disable function tracing of latency tracers"). I may just remove the damn thing and only add it back if somebody complains about it. -- Steve