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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id CFC88EDE9AC for ; Tue, 10 Sep 2024 18:41:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To: From:Date:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=z0T3FrUafPE9gDG5E0pO2NcprWhB8bu1wpQwOMx2SSk=; b=uPdmtjhVZVsG6ggbxpAoeEJMjf CmU7ZegX1qgMeCjWQ91xKXK9d38B0rjjX3TRiWNzXxwccjjeOy9mrhfMyOSAcZC3BzMi483obpHVp B8sExd44QMKLi0ifKFU+ZsBEmrx5idbNhHTDHg/3jWRq3Xj2t2RugspKp/QdD4rTHAWdAlosMQyNO ujnHHF4fWOK9v0ZcCMo66fMo6hHkoXQ3ANX+UTMqv5aDJ6Ts/oFy7gPsW3zQl0DiUaO3KFVcGKE87 cL1NgSZKCfYvUyEStLk1dBCmVSU0aBIJyqIoNg3a7mr57StUmNwVOsIYtJYufZPfksTt4Ucil1Yl7 jMujKqpA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1so5nk-00000006lf6-16UQ; Tue, 10 Sep 2024 18:41:20 +0000 Received: from nyc.source.kernel.org ([2604:1380:45d1:ec00::3]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1so5mi-00000006lST-3O3D for linux-arm-kernel@lists.infradead.org; Tue, 10 Sep 2024 18:40:18 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id 3B5BDA44630; Tue, 10 Sep 2024 18:40:08 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EAD08C4CEC3; Tue, 10 Sep 2024 18:40:13 +0000 (UTC) Date: Tue, 10 Sep 2024 14:40:15 -0400 From: Steven Rostedt To: Andrii Nakryiko Cc: Masami Hiramatsu , bpf , Linux trace kernel , adubey@linux.ibm.com, "Naveen N. Rao" , KP Singh , linux-arm-kernel , Mark Rutland , Will Deacon , Alexei Starovoitov , Catalin Marinas , Florent Revest , Puranjay Mohan Subject: Re: Unsupported CONFIG_FPROBE and CONFIG_RETHOOK on ARM64 Message-ID: <20240910144015.643dc6da@gandalf.local.home> In-Reply-To: References: X-Mailer: Claws Mail 3.20.0git84 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240910_114016_947976_51D1225F X-CRM114-Status: GOOD ( 12.73 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, 10 Sep 2024 11:23:29 -0700 Andrii Nakryiko wrote: > Masami, Steven, > > Does Linus have to be in CC to get any reply here? Come on, it's been > almost a full week. And we are busy getting ready for Plumbers. Go ahead Cc Linus, I'm sure he doesn't care, and you will likely just annoy him unless this is a regression. > > Maybe ARM64 folks have some context?... And hopefully desire to see > this through so that ARM64 doesn't stick out as a lesser-supported > platform as far as tracing goes compared to loongarch, s390x, and > powerpc (which just landed rethook support, see [2]). > > Note that there was already an implementation (see [1]), but for some > reason it never made it. > > [1] https://lore.kernel.org/bpf/164338038439.2429999.17564843625400931820.stgit@devnote2/ > [2] https://lore.kernel.org/bpf/172562357215.467568.2172858907419105155.b4-ty@ellerman.id.au/ Masami's fprobe work is near the top of my priority list, but there's been bugs reported that always take precedence over features. There's been fires to put out that has caused this to be delayed. There! I replied. -- Steve