Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp819035imm; Wed, 15 Aug 2018 06:47:38 -0700 (PDT) X-Google-Smtp-Source: AA+uWPw716rQ5lKdx3fdND0eXzqnuY8RtROZEWR2HDpJmPnczm+BlNFK0xVSPIxCPlrKV9ZRcnA9 X-Received: by 2002:a63:ca09:: with SMTP id n9-v6mr24844696pgi.287.1534340858255; Wed, 15 Aug 2018 06:47:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534340858; cv=none; d=google.com; s=arc-20160816; b=tn7pt+hJAaJh5baAa+IOW0lOy9CJ7+btzJYNDDdVLkaxI7zLD+ASzuFkwGOXVJbZEy HxhK88Hxo6sjGa8MwvH40LXLfMFHsVEYD9TyPloKkiVwowu0S6QxmZakYB4sK5B2OBP0 HuZ6m15YVxULd5yxio+bCtU5xI+YSftbszNqh1BDSSGlyVUtOfwm7O97UmX+ODCJH9ol rIf3K/vsA4tepKD0C7WySKVk2OQAOzZflF4dpq15QmIbEot9o/8cgB8fzrOmH1zCoZ8m X8L0FbS2OiYTJnj8rm3m+9Uf1XpdL39ttGlnUFXBVdbLSTSp+3SJq4XtdGeHqqvExW2R VE3w== 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:arc-authentication-results; bh=B/Z7UwIjNrytFGGE4NZI7DcmdPAfCxSavNAKj71Le4k=; b=V8GH4MlLgbIeCVWIB9L0mSxWwYtBSU31KnrefoaHlTVp5jko05ZY+eeeAME9m30Cg3 ESSTWrM2POx5Ta6g6wzBCwIGJym15zUqOcsvqIGo6vWiU0V6lt8FsDBHFyuezavznRE7 HgZIXl2SDdHOAu30zoa2ltDJxsWPqd4wsBlOxvvvg5Gn9nA/Met2p7bpLTVgv3shAMB5 NFzijo6RfNgIk6IoDNM/r8U5KnNU4Nr+MX9uxj1ilpXqwu5pjwZqYnL4TcANoBB5mhg2 nQJXCn5TBPJwLozZZ8WGuYx30pJnsa27XPqZQgSPn4HfRGS4aR5joPJAaVH3BePbZdri nGXw== 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 p187-v6si26287823pfp.27.2018.08.15.06.47.18; Wed, 15 Aug 2018 06:47:38 -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 S1729347AbeHOQih (ORCPT + 99 others); Wed, 15 Aug 2018 12:38:37 -0400 Received: from verein.lst.de ([213.95.11.211]:45219 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729125AbeHOQih (ORCPT ); Wed, 15 Aug 2018 12:38:37 -0400 Received: by newverein.lst.de (Postfix, from userid 2005) id 3C9B768E82; Wed, 15 Aug 2018 15:47:10 +0200 (CEST) Date: Wed, 15 Aug 2018 15:47:10 +0200 From: Torsten Duwe To: Steven Rostedt Cc: Julien Thierry , Will Deacon , Catalin Marinas , Ingo Molnar , Ard Biesheuvel , Arnd Bergmann , AKASHI Takahiro , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, live-patching@vger.kernel.org Subject: Re: [PATCH 1/3] arm64: implement ftrace with regs Message-ID: <20180815134710.GA27854@lst.de> References: <20180810160043.9E45568C76@newverein.lst.de> <20180810160223.D360D68C76@newverein.lst.de> <2b5c1092-2cc0-00ec-ba3d-341dc61452b4@arm.com> <20180813220315.6e8dfc9c@vmware.local.home> <20180814120433.1f5e8da1@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180814120433.1f5e8da1@gandalf.local.home> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [working on V2 with your feedback] On Tue, Aug 14, 2018 at 12:04:33PM -0400, Steven Rostedt wrote: > On Tue, 14 Aug 2018 09:33:52 +0100 > Julien Thierry wrote: > > >> Shouldn't this be an error? The option -fpatchable-function-entry has > > >> been added to the CC_FLAGS_FTRACE, so any call to the compiler is gonna > > >> break anyway. Or am I missing something? This should be the case. > OK, I see what you mean. If the resulting build wont boot, then yes > this should be an error and not a warning. No, there won't be a binary because the first gcc invocation with CC_FLAGS_FTRACE will error out. The alternatives are a makefile-warning followed by a gcc-error or just a makefile-error. The makefile warning or error should hint at the causing config option, that's the key point. Beyond that I don't have any preference. Torsten