From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7E57BC433FE for ; Tue, 22 Mar 2022 12:46:40 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233607AbiCVMsG (ORCPT ); Tue, 22 Mar 2022 08:48:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60542 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231920AbiCVMsF (ORCPT ); Tue, 22 Mar 2022 08:48:05 -0400 Received: from sin.source.kernel.org (sin.source.kernel.org [IPv6:2604:1380:40e1:4800::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 665401B7B4; Tue, 22 Mar 2022 05:46:38 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sin.source.kernel.org (Postfix) with ESMTPS id C9C8DCE1DE9; Tue, 22 Mar 2022 12:46:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id B14E7C340EC; Tue, 22 Mar 2022 12:46:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1647953195; bh=wZ3oIwVDZDmNROUcHtUdRyFl6dXJ+VpbUzC1mZmGrmc=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=muAtEfcagfShZa7+gWpyrzfPnx4sXjQXQFwVLQvC6ubXFFW/0cp1m/mYtM0/ajpPt u7HqTrzTAWnk5nOHD2WmnsfmoMIdv9O5kAI7JoSaGlrNEz+DjFbQc6S8xbx2NrSg/b JPNxbVKFHqcJcqBGPOpc5e01gvPIRUx9WK89A5txGJgpxPvrqMQO/0/J4lfQB65ksS V5JpShqoy7nErJeRQri/Mm08KQ2Uk8+UnEk4yc63cSXzKHfZ4hVEe10r3+GjthNBxN N2sSBsGBHZE5OQUCCcbfRH6gr31TxiV+gGPYk729iBrLl6zCTvJL7iLnCUMjMTzZDu qg5++8QToB6ZQ== Date: Tue, 22 Mar 2022 21:46:29 +0900 From: Masami Hiramatsu To: Peter Zijlstra Cc: Stephen Rothwell , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Linux Kernel Mailing List , Linux Next Mailing List , rostedt@goodmis.org, ast@kernel.org, hjl.tools@gmail.com, rick.p.edgecombe@intel.com, rppt@kernel.org, linux-toolchains@vger.kernel.org, Andrew.Cooper3@citrix.com, ndesaulniers@google.com Subject: Re: linux-next: build warnings after merge of the tip tree Message-Id: <20220322214629.2bf40306e3beba23d88d509f@kernel.org> In-Reply-To: References: <20220321140327.777f9554@canb.auug.org.au> <20220322143136.0e78366c3521b54b7b9385b8@kernel.org> X-Mailer: Sylpheed 3.7.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 Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Tue, 22 Mar 2022 13:17:18 +0100 Peter Zijlstra wrote: > On Tue, Mar 22, 2022 at 02:31:36PM +0900, Masami Hiramatsu wrote: > > > > But I still think it's fairly terrible to get a (flawed) carbon copy of > > > the kretprobe code. > > > > Indeed. I would like to replace the trampoline code of kretprobe with > > rethook, eventually. There is no reason why we keep the clone. > > (But I need more arch maintainers help for that, there are too many > > archs implemented kretprobes) > > CONFIG_KPROBE_ON_RETHOOK - and then implement archs one by one? Sounds good! Maybe we will see different data structure fields which depends on that config, but those are internal fields, so user will not access it. Thank you, -- Masami Hiramatsu