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 AA5773822B5 for ; Fri, 13 Mar 2026 21:10:09 +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=1773436209; cv=none; b=SbHi5oZzUw4k2SBbm6CYpQiJEhrwCq5upKesxR3h6myqRkxyg74zI7LHiEEsuAO21qLUM0Ki8dCgLavmxMQHviw9aRInerP9xfxPQjUMqYS52ALio1+nOhnYoszEMlzje+2uwpOQwj/Vdze+lI31I8EPJodkmRszbYAgjXrOoNw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773436209; c=relaxed/simple; bh=UWzAEdOzxGgl/flsaolDDVPA3mlkYHVZz9/m25AsM5A=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=PCy7tL9uf2X+9CZE8LetcNltIH6sUhSQDMpLu99cJixW7H+Sgx3yrBvyGu7L702v0S54Z31iAfvSf+ytOgCm160ItBKq/2WBDLmKqCol7lZnki8F9ozyWzlE0BgaMTALh6bvCxW+WZn5DlhF6W6+U9dGAiT8ccXdNP+Ukmiy1VI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=EsEoML0J; 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="EsEoML0J" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 07D3EC19421; Fri, 13 Mar 2026 21:10:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1773436209; bh=UWzAEdOzxGgl/flsaolDDVPA3mlkYHVZz9/m25AsM5A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=EsEoML0J7Dp2BKkU5bs0DFU2hrs43D5soJlMr7kP1asaFVGxCk3O/f7miyBtZGwx5 cpGmgiHcQZR2UipS1uJO1VOG7C2oavNviwNybAkRbGt8rTg4BS3vv2FXdqD76MSqfU RH0pnaG+EDG5AIyjQWq786R2kbq233WZNdtbEeTO2XHAr5ykeQ4P2GyG+8imJVy7Id idxmgPvVkayEYcHcc5nF9Zft2X9Wy2TjihPOJghzXfS/8Z76K6N/0INl/wKZoiC19T NXdSPiXVTfsY/Rypa1pWqT19pgqnzc2N94f5qd31l2GQebxYMeh2wGK0SBIFEqEwKC Io131ThRuqQLw== Date: Fri, 13 Mar 2026 14:10:07 -0700 From: Namhyung Kim To: Ian Rogers Cc: Arnaldo Melo , Arnaldo Carvalho de Melo , Thomas Richter , "linux-perf-use." , Jan Polensky Subject: Re: perf stat issue with 7.0.0rc3 Message-ID: References: <66d0366b-8690-4bde-aba4-1d51f278dfa1@linux.ibm.com> <957241A0-E5C8-417C-98B7-B6E1EAFE19B1@gmail.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 In-Reply-To: Hello, On Fri, Mar 13, 2026 at 11:27:30AM -0700, Ian Rogers wrote: > > >No worries, presumably if I'd been monitoring: > > >https://web.git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git/log/?h=tmp.perf-tools > > >I'd have seen it was missing. Perhaps you can give a heads up to check > > >for missing patches when assembling the PRs. I rarely look at > > >perf-tools.git as perf-tools-next.git is where all the action is :-) > > >Actually, I vibe coded a script that may work to automate this: > > >``` > > > > > > Well, if those patches are ok for perf-tools, i.e. are fixes for bugs introduced in the current merge window or urgent fixes for longstanding bugs, they shouldn't be in perf-tools-next, they should be in perf-tools to be merger in the current merge window. > > > > Coordination in triaging via an Acked-by/Reviewed-by pointing out it's something for the current merge window, something I do, is what we should strive to do. > > > > When I notice something that's needed for the current window that's been processed by Namhyung for perf-tools-next, I merge it as well (as will be in this case and maybe in the others that you pointed out, thanks, I'll check each one). > > > > No problem with that, better be in both branches than to get missed :-) > > Thanks! In the patches tagged as "fixes," I think these 2 also need picking up: > > commit aa6a6a2d16c1e2e27e986936369959d70316199f ("perf parse-events: > Fix big-endian 'overwrite' by writing") to fix s390. > commit 06ec44c2aa2ef15fd56f9808b6cf7495e1fbd8ec ("perf kvm stat: Fix > relative paths for including headers") for non-x86 builds. > > The other patches are test fixes or address malloc failures that > shouldn't really happen, so they are not a priority. Great! Thanks for taking care of this. I'll be more careful when merging fixes. Thanks, Namhyung