linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm64: Export save_stack_trace_tsk()
Date: Wed, 14 Jun 2017 11:06:37 +0100	[thread overview]
Message-ID: <20170614100636.GA16190@arm.com> (raw)
In-Reply-To: <20170613181603.GE4902@n2100.armlinux.org.uk>

On Tue, Jun 13, 2017 at 07:16:03PM +0100, Russell King - ARM Linux wrote:
> On Tue, Jun 13, 2017 at 06:44:06PM +0100, Will Deacon wrote:
> > On Tue, Jun 13, 2017 at 10:33:08AM -0700, Dustin Brown wrote:
> > > To aid in debugging driver modules, export save_stack_trace_tsk() for
> > > the ARM64 architecture.
> > > ---
> > >  arch/arm64/kernel/stacktrace.c | 1 +
> > >  1 file changed, 1 insertion(+)
> > 
> > Please can you repost with your Signed-off-by line added to the patch? I
> > can't merge anything from you without that.
> 
> I think it would also be a good thing to have a little more information
> about how this is being used in driver modules.

That would certainly help to motivate the change; I was just going by the
fact that most other architectures export this symbol and therefore it is
assumedly useful to somebody.

> If it's for ad-hoc debugging, then I see no reason for it to be merged
> into mainline kernels just for the utility of people adding code to
> drivers to perform that debug - they might as well temporarily add the
> export at the same time IMHO.

A quick look at the Debian archive suggests that it's used by "systemtap"
(although this seems to be part of an autoconf helper) and "kpatch".

Dustin -- do you have another use-case behind this?

Will

  parent reply	other threads:[~2017-06-14 10:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 22:24 [PATCH] Export save_stack_trace_tsk for ARM and ARM64 Dustin Brown
2017-06-13  8:50 ` Will Deacon
2017-06-13 17:33   ` [PATCH 1/2] arm: Export save_stack_trace_tsk() Dustin Brown
2017-06-13 17:33     ` [PATCH 2/2] arm64: " Dustin Brown
2017-06-13 17:44       ` Will Deacon
2017-06-13 18:16         ` Russell King - ARM Linux
2017-06-13 18:40           ` [PATCH 1/2] arm: " Dustin Brown
2017-06-13 18:40             ` [PATCH 2/2] arm64: " Dustin Brown
2017-07-12 18:06             ` [PATCH 1/2] arm: " Dustin Brown
2017-06-14 10:06           ` Will Deacon [this message]
2017-06-14 16:51             ` [PATCH 2/2] arm64: " Dustin Brown

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=20170614100636.GA16190@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).