Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp172533imm; Mon, 1 Oct 2018 08:15:03 -0700 (PDT) X-Google-Smtp-Source: ACcGV60g24qzk8etLLab2O0+ykr0Pfz5kFMnmSosU+hoX8LrdXRWKggLiTb8vf59o1OuQq0bsyV9 X-Received: by 2002:a63:f744:: with SMTP id f4-v6mr10756311pgk.410.1538406903118; Mon, 01 Oct 2018 08:15:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538406903; cv=none; d=google.com; s=arc-20160816; b=ywtSCtHSHuOqUN7kTeXyBXvHwXVJKe+vaywqdn5AAEPpCc5x9o31goOpqmwcvsBSA8 8fjYwXvQHWJq5tsW6mK/BrBrPmIbGH2bawlLFkr6L/KnGeodUgnUQ83WKMsWcLfbkrSt iVf8DhyYzw0nRBPKpzua32okflOrEMfYYGd+4Lef2MdBq4K86TNPJNWLysFyQvp88/aY 25mYGHx7HfljP/Cp0YlPags/u+7AGf4+riJoY3JCypcYWbeem7FVU1Y+G8V7I7kA0FzE a8Eu9rTOIksVij/qJB+RPvltBVkjHA3nyZPs60gbGL8x3FYE+khFZ+3EhuPcb9L6EPj1 FLhA== 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=VYj35aabEQeA3YArvN5dvNlTBSu7E2zQgOQZxE3pdpU=; b=ENYdwoZgV96L8AKN5ChnB+XJMRLqrUBO+LBJPCL4A3nzvBozjxypPg9NRZ+7eLsZeu iFqXRZ7plx8ectQlX6tpj+mrzYOuQBmf+ckJym+H0fTVDBttKLRISEJxjPLmZsVzVCJi eRS5DONDuGqjyyr4kajSPJwhzh6gHcfIq16YF9t42HaEElONjP2zi2iOyBzk16gSyJsv /zXHFZK86vts8qu0/2OUaHlk55B1b2A/dh6Ti3TaRHx/1+WL8N6GnwzXJSmDmiDA6Akt w9clKNSuGqHRgH6uVoKCHSVrAL+cV3ke+c2kntTz7vVtKLWUi9oqXFNLTacU/0VNcCuM suhA== 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 l185-v6si13355418pfl.134.2018.10.01.08.14.36; Mon, 01 Oct 2018 08:15:03 -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 S1729620AbeJAVwZ (ORCPT + 99 others); Mon, 1 Oct 2018 17:52:25 -0400 Received: from mail.kernel.org ([198.145.29.99]:59062 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729531AbeJAVwZ (ORCPT ); Mon, 1 Oct 2018 17:52:25 -0400 Received: from gandalf.local.home (cpe-66-24-56-78.stny.res.rr.com [66.24.56.78]) (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 BF94F208D9; Mon, 1 Oct 2018 15:14:07 +0000 (UTC) Date: Mon, 1 Oct 2018 11:14:06 -0400 From: Steven Rostedt To: Torsten Duwe Cc: Ard Biesheuvel , Masami Hiramatsu , Will Deacon , Catalin Marinas , Julien Thierry , Josh Poimboeuf , Ingo Molnar , Arnd Bergmann , AKASHI Takahiro , linux-arm-kernel , Linux Kernel Mailing List , live-patching@vger.kernel.org Subject: Re: [PATCH v3 1/4] DYNAMIC_FTRACE configurable with and without REGS Message-ID: <20181001111406.0c799813@gandalf.local.home> In-Reply-To: <20181001151037.GB2634@lst.de> References: <20181001140910.086E768BC7@newverein.lst.de> <20181001141643.331EE68BC7@newverein.lst.de> <20181001150353.GA2634@lst.de> <20181001151037.GB2634@lst.de> X-Mailer: Claws Mail 3.16.0 (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 Mon, 1 Oct 2018 17:10:37 +0200 Torsten Duwe wrote: > On Mon, Oct 01, 2018 at 05:06:06PM +0200, Ard Biesheuvel wrote: > > On 1 October 2018 at 17:03, Torsten Duwe wrote: > > > On Mon, Oct 01, 2018 at 04:52:27PM +0200, Ard Biesheuvel wrote: > > >> > > >> I guess we now have Kbuild/Kconfig support for this, no? I mean, we > > >> can now show/hide options depending on the capabilities of the > > >> toolchain. > > > > > > Config options depending on flags availability? > > > > > Yes. Note that 'make menuconfig' now prints the compiler version at > > the top, and kconfig options can now 'depend' on compiler features, > > Ah, cool, got it. So unless anyone else thinks this patch is useful, > feel free to disregard it ;-) Point taken. > Yes, please don't apply this patch. Have the build system figure out if the tool chain can handle it or not. -- Steve