From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5412A246781; Fri, 15 May 2026 00:28:40 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778804921; cv=none; b=qq8o0mFy56+/X/c33Iuw5tZ7v2S/d3fBVFzFXWMuntuehjT1OrjR/5uv4Ae+y4T/ZosyygUSAg49UYceRdOkF4HqCtpEIcMtkW5IodSPCaWf8KI7hvX8nOlXJiArO8XOx59I1gda+T+0voc/v41BjIvyHExfOgAcESFsBrC50Jc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778804921; c=relaxed/simple; bh=1pZiWvBhnqpkHnvABTbPJV3MrqThd/XnMjqELMyQAfk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=h8AZYvn4MOJUxLleuEig++VUewCu8ZG/jb/kXN0w7hfc9XN0zSEwPceqlVYLbUgf3Jpji2FhquN8FoSZe0+1faEJf3lPI/udi7l1dysQhDylwOph1Ro/lklJjuA+bbkv20fEDtw3nsiab0oMPBZA6or9jWy8Ormpqmzqkziy2IY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=gDZopiaX; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="gDZopiaX" 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> Precedence: bulk X-Mailing-List: linux-perf-users@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: 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