From: Miroslav Benes <mbenes@suse.cz>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
heiko.carstens@de.ibm.com, gor@linux.ibm.com,
borntraeger@de.ibm.com, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, jikos@kernel.org, pmladek@suse.com,
nstange@suse.de, live-patching@vger.kernel.org
Subject: Re: [PATCH] s390/livepatch: Implement reliable stack tracing for the consistency model
Date: Tue, 13 Aug 2019 16:02:17 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.1908131602040.10477@pobox.suse.cz> (raw)
In-Reply-To: <20190728203053.q3pafkwnzm5j3ccs@treble>
On Sun, 28 Jul 2019, Josh Poimboeuf wrote:
> On Wed, Jul 17, 2019 at 01:01:27PM +0200, Miroslav Benes wrote:
> > > On a related note, do you think it would be feasible to extend (in
> > > another patchset) the reliable stack unwinding code a bit so that we
> > > could feed it pre-baked stacks ... then we could verify that the code
> > > was finding interesting scenarios. That was a passing thought I had
> > > back when Nicolai and I were debugging the ppc64le exception frame
> > > marker bug, but didn't think it worth the time/effort at the time.
> >
> > That is an interesting thought. It would help the testing a lot. I will
> > make a note in my todo list.
>
> Another idea I had for reliable unwinder testing: add a
> CONFIG_RELIABLE_STACKTRACE_DEBUG option which does a periodic stack
> trace and warns if it doesn't reach the end. It could triggered from a
> periodic NMI, or from schedule().
Noted as well.
Miroslav
next prev parent reply other threads:[~2019-08-13 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 10:59 [PATCH] s390/livepatch: Implement reliable stack tracing for the consistency model Miroslav Benes
2019-07-16 18:45 ` Joe Lawrence
2019-07-17 11:01 ` Miroslav Benes
2019-07-28 20:30 ` Josh Poimboeuf
2019-08-13 14:02 ` Miroslav Benes [this message]
2019-07-28 20:44 ` Josh Poimboeuf
2019-08-14 10:52 ` Miroslav Benes
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=alpine.LSU.2.21.1908131602040.10477@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=nstange@suse.de \
--cc=pmladek@suse.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).