From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Pratyush Anand <panand@redhat.com>,
schwidefsky@de.ibm.com, linux-s390@vger.kernel.org,
Chunyu Hu <chuhu@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] s390:ftrace: add save_stack_trace_regs()
Date: Fri, 29 Jan 2016 18:12:49 +0100 [thread overview]
Message-ID: <20160129171249.GG3896@osiris> (raw)
In-Reply-To: <20160129115659.1b31f9c5@gandalf.local.home>
On Fri, Jan 29, 2016 at 11:56:59AM -0500, Steven Rostedt wrote:
> On Fri, 29 Jan 2016 17:49:18 +0100
> Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
>
> > Which looks much better. The stack tracer also works again!
>
> Great! Although, it shouldn't have affected the stack tracing of kprobe
> events :-/
Yes, you're absolutely right. I mixed up my trees (one 4.4 based and one
Linus' master).
> Although the previous commit I showed would.
So, the save_stack_trace_regs() patch from Pratyush does work
out-of-the-box on Linus' master tree and the stack tracer only if your
additional patch is applied.
Sorry for the confusion!
next prev parent reply other threads:[~2016-01-29 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 5:20 [PATCH] s390:ftrace: add save_stack_trace_regs() Pratyush Anand
2016-01-29 5:20 ` Pratyush Anand
2016-01-29 8:54 ` Heiko Carstens
2016-01-29 12:57 ` Heiko Carstens
2016-01-29 13:59 ` Steven Rostedt
2016-01-29 14:45 ` Heiko Carstens
2016-01-29 15:22 ` Steven Rostedt
2016-01-29 16:49 ` Heiko Carstens
2016-01-29 16:56 ` Steven Rostedt
2016-01-29 17:12 ` Heiko Carstens [this message]
2016-02-01 9:00 ` 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=20160129171249.GG3896@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=chuhu@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=panand@redhat.com \
--cc=rostedt@goodmis.org \
--cc=schwidefsky@de.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.