From: "Jose E. Marchesi" <jemarch@gnu.org>
To: Steven Rostedt <rostedt@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, jremus@linux.ibm.com,
jpoimboe@kernel.org, peterz@infradead.org, mingo@kernel.org,
jolsa@kernel.org, acme@kernel.org, namhyung@kernel.org,
tglx@linutronix.de, andrii@kernel.org, indu.bhagat@oracle.com,
beaub@linux.microsoft.com, torvalds@linux-foundation.org,
akpm@linux-foundation.org, fweimer@redhat.com, kees@kernel.org,
codonell@redhat.com, sam@gentoo.org, dylanbhatch@google.com,
bp@alien8.de, dave.hansen@linux.intel.com, david@redhat.com,
hpa@zytor.com, Liam.Howlett@oracle.com,
lorenzo.stoakes@oracle.com, mhocko@suse.com, rppt@kernel.org,
surenb@google.com, vbabka@suse.cz, hca@linux.ibm.com,
gor@linux.ibm.com
Subject: Re: [RFC][PATCH] unwind: Add stacktrace_setup system call
Date: Fri, 08 May 2026 09:32:08 +0200 [thread overview]
Message-ID: <873402cq6f.fsf@gnu.org> (raw)
In-Reply-To: <20260507215751.0c286695@fedora>
> On Thu, 07 May 2026 14:37:36 +0200
> "Jose E. Marchesi" <jemarch@gnu.org> wrote:
>
>> FWIW passing start and end of both the tracing data and the text segment
>> it covers seems reasonable to me. This covers the case in which the
>> same tracing data describes several text segments, which can happen with
>> SFrame and other similar formats.
>
> Just so I understand you. You are suggesting to pass in the end address
> instead of the length?
No no, was talking conceptually. Denoting the end of the region by its
length is better. I see no reason to do otherwise in this case.
next prev parent reply other threads:[~2026-05-08 7:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 15:43 [RFC][PATCH] unwind: Add stacktrace_setup system call Steven Rostedt
2026-04-29 15:47 ` Steven Rostedt
2026-04-29 18:32 ` Mathieu Desnoyers
2026-04-30 7:26 ` Geert Uytterhoeven
2026-04-29 18:42 ` Mathieu Desnoyers
2026-04-29 18:55 ` Steven Rostedt
2026-04-29 18:58 ` Steven Rostedt
2026-04-29 20:03 ` Steven Rostedt
2026-04-30 16:23 ` Jens Remus
2026-04-30 16:26 ` Mathieu Desnoyers
2026-04-30 17:33 ` Steven Rostedt
2026-04-30 17:38 ` Steven Rostedt
2026-05-07 12:37 ` Jose E. Marchesi
2026-05-08 1:57 ` Steven Rostedt
2026-05-08 7:32 ` Jose E. Marchesi [this message]
2026-05-08 7:46 ` Jens Remus
2026-05-12 16:47 ` Steven Rostedt
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=873402cq6f.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=Liam.Howlett@oracle.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=bp@alien8.de \
--cc=codonell@redhat.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=dylanbhatch@google.com \
--cc=fweimer@redhat.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=indu.bhagat@oracle.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=jremus@linux.ibm.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@kernel.org \
--cc=rppt@kernel.org \
--cc=sam@gentoo.org \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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