From: Jiri Kosina <jikos@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
live-patching@vger.kernel.org,
Balbir Singh <bsingharora@gmail.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Nicolai Stange <nstange@suse.de>, Torsten Duwe <duwe@lst.de>
Subject: Re: [PATCH 0/4] powerpc/livepatch: reliable stack unwinder fixes
Date: Wed, 30 Jan 2019 14:28:43 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.1901301427320.6626@cbobk.fhfr.pm> (raw)
In-Reply-To: <87y372pc75.fsf@concordia.ellerman.id.au>
On Wed, 30 Jan 2019, Michael Ellerman wrote:
> I'm happy to take it, unless there's some reason you'd rather it go via
> the LP tree?
As this is more about reliable stack unwinding than live patching per se
(which is only a user of that facility), I'd actually slightly prefer if
it goes via your tree.
Thanks,
--
Jiri Kosina
SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Kosina <jikos@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
Nicolai Stange <nstange@suse.de>,
linux-kernel@vger.kernel.org, Torsten Duwe <duwe@lst.de>,
Josh Poimboeuf <jpoimboe@redhat.com>,
live-patching@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/4] powerpc/livepatch: reliable stack unwinder fixes
Date: Wed, 30 Jan 2019 14:28:43 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.1901301427320.6626@cbobk.fhfr.pm> (raw)
In-Reply-To: <87y372pc75.fsf@concordia.ellerman.id.au>
On Wed, 30 Jan 2019, Michael Ellerman wrote:
> I'm happy to take it, unless there's some reason you'd rather it go via
> the LP tree?
As this is more about reliable stack unwinding than live patching per se
(which is only a user of that facility), I'd actually slightly prefer if
it goes via your tree.
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2019-01-30 13:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 15:57 [PATCH 0/4] powerpc/livepatch: reliable stack unwinder fixes Joe Lawrence
2019-01-22 15:57 ` Joe Lawrence
2019-01-22 15:57 ` [PATCH 1/4] powerpc/64s: Clear on-stack exception marker upon exception return Joe Lawrence
2019-01-22 15:57 ` Joe Lawrence
2019-01-30 12:27 ` Michael Ellerman
2019-01-30 12:27 ` Michael Ellerman
2019-01-30 17:18 ` Nicolai Stange
2019-01-30 17:18 ` Nicolai Stange
2019-01-31 5:46 ` Michael Ellerman
2019-01-31 5:46 ` Michael Ellerman
2019-02-02 1:14 ` Balbir Singh
2019-02-02 1:14 ` Balbir Singh
2019-02-02 3:42 ` Balbir Singh
2019-02-02 3:42 ` Balbir Singh
2019-02-05 11:24 ` Michael Ellerman
2019-02-05 11:24 ` Michael Ellerman
2019-02-06 2:48 ` Balbir Singh
2019-02-06 2:48 ` Balbir Singh
2019-02-06 4:44 ` Michael Ellerman
2019-02-06 4:44 ` Michael Ellerman
2019-02-06 8:45 ` Balbir Singh
2019-02-06 8:45 ` Balbir Singh
2019-02-08 13:02 ` [1/4] " Michael Ellerman
2019-02-08 13:02 ` Michael Ellerman
2019-01-22 15:57 ` [PATCH 2/4] powerpc/livepatch: relax reliable stack tracer checks for first-frame Joe Lawrence
2019-01-22 15:57 ` Joe Lawrence
2019-01-22 15:57 ` [PATCH 3/4] powerpc/livepatch: small cleanups in save_stack_trace_tsk_reliable() Joe Lawrence
2019-01-22 15:57 ` Joe Lawrence
2019-01-22 15:57 ` [PATCH 4/4] powerpc/livepatch: return -ERRNO values " Joe Lawrence
2019-01-22 15:57 ` Joe Lawrence
2019-02-02 0:59 ` Balbir Singh
2019-02-02 0:59 ` Balbir Singh
2019-01-29 21:10 ` [PATCH 0/4] powerpc/livepatch: reliable stack unwinder fixes Josh Poimboeuf
2019-01-29 21:10 ` Josh Poimboeuf
2019-01-29 23:50 ` Jiri Kosina
2019-01-29 23:50 ` Jiri Kosina
2019-01-30 12:22 ` Michael Ellerman
2019-01-30 12:22 ` Michael Ellerman
2019-01-30 13:28 ` Jiri Kosina [this message]
2019-01-30 13:28 ` Jiri Kosina
2019-01-31 5:46 ` Michael Ellerman
2019-01-31 5:46 ` Michael Ellerman
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=nycvar.YFH.7.76.1901301427320.6626@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=bsingharora@gmail.com \
--cc=duwe@lst.de \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nstange@suse.de \
/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.