From: Heiko Carstens <hca@linux.ibm.com>
To: Daan De Meyer <daan.j.demeyer@gmail.com>
Cc: linux-s390@vger.kernel.org, linux-perf-users@vger.kernel.org,
"dcavalca@meta.com" <dcavalca@meta.com>,
ngompa@fedoraproject.org, Andreas Krebbel <krebbel@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Sumanth Korikkar <sumanthk@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: s390x stack unwinding with perf?
Date: Fri, 27 Oct 2023 12:09:25 +0200 [thread overview]
Message-ID: <20231027100925.9071-B-hca@linux.ibm.com> (raw)
In-Reply-To: <CAO8sHckF_D+SjvGySsGHOpOcdy6y7pwQEF9SfV3sw4Ye4_sCKA@mail.gmail.com>
On Fri, Oct 27, 2023 at 10:00:53AM +0200, Daan De Meyer wrote:
>
> If the kernel gets support for s390x user space unwinding using the backchain,
> we'll propose to enable -mbackchain in the default compilation flags for Fedora
> so that s390x on Fedora will have the same profiling experience as x86-64, arm64
> and ppc64. For now we'll keep the status quo since compiling with the backchain
> doesn't provide any benefit until the kernel unwinder can unwind user
> space stacks
> using it.
>
> Thanks for clarifying the current state of user space stack unwinding on s390x!
We will implement the missing pieces and let you know when things are
supposed to work.
next prev parent reply other threads:[~2023-10-27 10:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 12:30 s390x stack unwinding with perf? Daan De Meyer
2023-10-26 14:56 ` Heiko Carstens
2023-10-26 14:58 ` Neal Gompa
2023-10-27 8:00 ` Daan De Meyer
2023-10-27 10:09 ` Heiko Carstens [this message]
2023-10-27 15:22 ` Neal Gompa
2023-10-30 12:35 ` Heiko Carstens
2023-10-30 13:19 ` Neal Gompa
2023-11-09 14:48 ` Heiko Carstens
2023-12-20 12:58 ` Daan De Meyer
2024-01-03 15:48 ` Heiko Carstens
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=20231027100925.9071-B-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=daan.j.demeyer@gmail.com \
--cc=dcavalca@meta.com \
--cc=gor@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=krebbel@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=ngompa@fedoraproject.org \
--cc=sumanthk@linux.ibm.com \
--cc=tmricht@linux.ibm.com \
/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).