linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Jens Remus <jremus@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	x86@kernel.org, Steven Rostedt <rostedt@kernel.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Indu Bhagat <indu.bhagat@oracle.com>,
	"Jose E. Marchesi" <jemarch@gnu.org>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v4 0/4] unwind_user: Cleanups
Date: Mon, 8 Dec 2025 20:36:05 +0100	[thread overview]
Message-ID: <20251208193605.GG3707891@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251208160352.1363040-1-jremus@linux.ibm.com>

On Mon, Dec 08, 2025 at 05:03:48PM +0100, Jens Remus wrote:
> This patch series applies on top of Peter Zijlstras' latest unwind user
> enhancements (and perf deferred callchain support) on his tip perf/core
> branch:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
> 
> Which has already been merged to tip/master and linux-next/master.

Right, that should be empty now :-)


> Jens Remus (4):
>   unwind_user: Enhance comments on get CFA, FP, and RA
>   unwind_user/fp: Use dummies instead of ifdef
>   x86/unwind_user: Guard unwind_user_word_size() by UNWIND_USER
>   x86/unwind_user: Simplify unwind_user_word_size()
> 
>  arch/x86/include/asm/unwind_user.h | 27 ++++++++++++++-------------
>  include/linux/unwind_user.h        | 18 ++++++++++++++++--
>  kernel/unwind/user.c               | 12 ++++--------
>  3 files changed, 34 insertions(+), 23 deletions(-)

I'll go stick these patches in tip/perf/core after rc1 or so, no real
hurry with these, right?

  parent reply	other threads:[~2025-12-08 19:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08 16:03 [PATCH v4 0/4] unwind_user: Cleanups Jens Remus
2025-12-08 16:03 ` [PATCH v4 1/4] unwind_user: Enhance comments on get CFA, FP, and RA Jens Remus
2025-12-08 16:03 ` [PATCH v4 2/4] unwind_user/fp: Use dummies instead of ifdef Jens Remus
2025-12-08 16:03 ` [PATCH v4 3/4] x86/unwind_user: Guard unwind_user_word_size() by UNWIND_USER Jens Remus
2025-12-08 16:03 ` [PATCH v4 4/4] x86/unwind_user: Simplify unwind_user_word_size() Jens Remus
2025-12-08 19:36 ` Peter Zijlstra [this message]
2025-12-09  9:10   ` [PATCH v4 0/4] unwind_user: Cleanups Jens Remus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251208193605.GG3707891@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=iii@linux.ibm.com \
    --cc=indu.bhagat@oracle.com \
    --cc=jemarch@gnu.org \
    --cc=jpoimboe@kernel.org \
    --cc=jremus@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=rostedt@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).