From: Torsten Duwe <duwe@lst.de>
To: Miroslav Benes <mbenes@suse.cz>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Jiri Kosina <jkosina@suse.cz>,
Balbir Singh <bsingharora@gmail.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
live-patching@vger.kernel.org
Subject: Re: [PATCH] On ppc64le we HAVE_RELIABLE_STACKTRACE
Date: Tue, 12 Dec 2017 14:02:46 +0100 [thread overview]
Message-ID: <20171212130246.GA4391@lst.de> (raw)
In-Reply-To: <alpine.LSU.2.21.1712121308440.21907@pobox.suse.cz>
On Tue, Dec 12, 2017 at 01:12:37PM +0100, Miroslav Benes wrote:
>
> I think that this is not enough. You need to also implement
> save_stack_trace_tsk_reliable() for powerpc defined as __weak in
> kernel/stacktrace.c. See arch/x86/kernel/stacktrace.c for reference, but I
> think it would be much much simpler here given the changelog description.
Is there an exhaustive, definite, non-x86-centric description of the cases
this function needs to look for? Maybe some sort of formal specification?
Torsten
next prev parent reply other threads:[~2017-12-12 13:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 15:25 [PATCH v2] kernel/module_64.c: Add REL24 relocation support of livepatch symbols Kamalesh Babulal
2017-10-05 6:56 ` Naveen N . Rao
2017-10-05 12:43 ` Torsten Duwe
2017-10-06 5:43 ` Kamalesh Babulal
2017-10-11 9:44 ` Kamalesh Babulal
2017-10-06 5:57 ` Kamalesh Babulal
2017-10-17 14:47 ` Torsten Duwe
2017-10-18 6:17 ` Kamalesh Babulal
2017-10-20 12:07 ` Torsten Duwe
2017-10-21 0:59 ` Balbir Singh
2017-10-23 8:19 ` Kamalesh Babulal
2017-12-12 11:39 ` [PATCH] On ppc64le we HAVE_RELIABLE_STACKTRACE Torsten Duwe
2017-12-12 12:12 ` Miroslav Benes
2017-12-12 13:02 ` Torsten Duwe [this message]
2018-02-27 16:09 ` [PATCH 2/2] ppc64le save_stack_trace_tsk_reliable (Was: HAVE_RELIABLE_STACKTRACE) Torsten Duwe
2018-03-08 21:43 ` Balbir Singh
2018-03-09 15:54 ` Torsten Duwe
2017-12-12 14:05 ` [PATCH] On ppc64le we HAVE_RELIABLE_STACKTRACE Josh Poimboeuf
2017-12-15 9:40 ` Nicholas Piggin
2017-12-18 2:58 ` Josh Poimboeuf
2017-12-18 3:39 ` Balbir Singh
2017-12-18 4:01 ` Josh Poimboeuf
2017-12-18 5:33 ` Nicholas Piggin
2017-12-18 18:56 ` Josh Poimboeuf
2017-12-19 2:46 ` Nicholas Piggin
2017-12-19 11:28 ` Torsten Duwe
2017-12-19 21:46 ` Josh Poimboeuf
2017-12-21 12:10 ` Michael Ellerman
2017-12-23 4:00 ` Josh Poimboeuf
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=20171212130246.GA4391@lst.de \
--to=duwe@lst.de \
--cc=bsingharora@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpe@ellerman.id.au \
/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.