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 655B8CD4F39 for ; Fri, 15 May 2026 00:28:51 +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:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References: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=DPlLXz0Gi7CqHPT1NLnWDqwIMSLmTM9cbGxCEnUy2oE=; b=pxwTmRVmeolQazXzQQFTxGxDlQ 2jisjJ2WlhpckrHfbkWbyZp8IR1Qk+pvPxLzBxayiO4eqLdLVC9W5+ByMkERJWSs/zyGGOAuoqYdU adUV59Isg+7xBbj9NwZxSH78PTe2QvrJSH8A6VvJ18s5eNLcyzJ2Tpiu+BGoxWQLzMotsIhX5E8Uy B0TMCLGJL0O6ZUkCNd2SH2PlochKEd5SPz7uEzybwXhvYeGXqQpF4NLTpjuTs5lRx+GHeQPQtewhk okZ0aqdOayFdRMNGdnnZ6LZaNM0L4QZ0+6XtiYnPHmtI21501DZC/k/WElHPExlSSfMIUyK4kdRhG MTBvUSyA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wNgQ0-00000006uyR-20zY; Fri, 15 May 2026 00:28:44 +0000 Received: from sea.source.kernel.org ([172.234.252.31]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wNgPx-00000006uxs-2BT6; Fri, 15 May 2026 00:28:42 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id D861044301; Fri, 15 May 2026 00:28:40 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 24972C2BCB3; Fri, 15 May 2026 00:28:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1778804920; bh=1pZiWvBhnqpkHnvABTbPJV3MrqThd/XnMjqELMyQAfk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=gDZopiaXEuLmbxRVtu2LNZBW8ZsvcPy0oNkp+Sw2hi05Y+eATPkT0ax3t/rkKz1gV 8sZ26tsyVqPB2tGkdcea9zSEsCh74+BTGl/b2UGintZqO/9GHoeAe4SDMJpqi4l49S maTiw9VeGOHgeayLdwfRrgvLneG4C0RmisI2JKZRSVH4i/7HVjWr/TaVhaQiMXDbEh E4O+ZrYzW0IFwdAXnMRYmofaJtYCAxObDvuVrAObK6OO2nBFqPpE3dUirDK2na9W15 JhymhkelrgSjLaTNGj4Zw8c+PGan8coxx4/gR4Jkl6PWrP/aaSrAL6Rt2jnlC7NKHZ qyZpUCYkoeOCw== Date: Thu, 14 May 2026 21:28:37 -0300 From: Arnaldo Carvalho de Melo To: Ian Rogers Cc: adrian.hunter@intel.com, dapeng1.mi@linux.intel.com, james.clark@linaro.org, namhyung@kernel.org, Florian Fainelli , Li Guan , 9erthalion6@gmail.com, alex@ghiti.fr, alexander.shishkin@linux.intel.com, andrew.jones@oss.qualcomm.com, aou@eecs.berkeley.edu, atrajeev@linux.ibm.com, howardchu95@gmail.com, john.g.garry@oracle.com, jolsa@kernel.org, leo.yan@linux.dev, libunwind-devel@nongnu.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, linux-riscv@lists.infradead.org, mingo@redhat.com, palmer@dabbelt.com, peterz@infradead.org, pjw@kernel.org, shimin.guo@skydio.com, tglozar@redhat.com, tmricht@linux.ibm.com, will@kernel.org Subject: Re: [PATCH v5 0/7] perf libunwind multiple remote support Message-ID: References: <20260413024805.1316480-1-irogers@google.com> <20260513233151.572332-1-irogers@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260514_172841_600250_F89E0CEF X-CRM114-Status: GOOD ( 27.50 ) 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 Thu, May 14, 2026 at 09:01:18PM -0300, Arnaldo Carvalho de Melo wrote: > On Thu, May 14, 2026 at 09:51:09AM -0700, Ian Rogers wrote: > > On Wed, May 13, 2026 at 4:32 PM Ian Rogers wrote: > > > Fix the libunwind build for when libdw and libunwind are feature > > > detected, currently failing with a duplicate symbol. > > > > > > Refactor the libunwind support so that whenever a remote target is > > > available, perf functions using the ELF machine can use that remote > > > target regardless of what the host/local machine is. Migrate existing > > > libunwind supported architectures like powerpc, arm64 and loongarch so > > > that they can work in a cross-architecture way. Add support for > > > RISC-V. Make the code more regular in function names, etc. and avoid > > > including a C-file. This increases the lines of code. It is similar in > > > style to the unwind-libdw implementation. It is hoped that the more > > > uniform nature of the code will help with refactoring the perf > > > registers for SIMD/APX support. > > > > > > Aside from local host testing these patches are under tested, in part > > > as I'm failing to see how to build libunwind with support for multiple > > > remote targets. Please could I get help in testing. > > > > So the patches failed to apply in Sashiko: > > https://sashiko.dev/#/patchset/20260513233151.572332-1-irogers%40google.com > > The baseline logs show perf-tools-next was at commit 8c8f20936143 > > ("perf build: Remove NO_GTK2 build test") which is 6 patches > > out-of-date compared to the current tip these patches are against. I > > ran Sashiko locally, so I don't expect a huge amount from the reviews. > > Currently Sashiko is catching up with a backlog because its tokens > > have a lower priority and there was high load earlier in the week. > > Anyway, I could repost the patches for Sashiko review but given the > > backlog I think that would just create noise at the moment. Hopefully > > I can get human review so we can move forward with merging these > > improvements. > > Trying to apply it now, will also run sashiko locally. Its in perf-tools-next tmp.perf-tools-next, Running build tests now and will let sashiko running locally, probably will push out tomorrow morning if nothing major is reported. To make progress I think we can go on addressing some Sashiko reviews with followup series otherwise it drags for a long time. - Arnaldo