From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Torsten Duwe <duwe@lst.de>, Jiri Kosina <jikos@kernel.org>,
Miroslav Benes <mbenes@suse.cz>,
linuxppc-dev@ozlabs.org, bsingharora@gmail.com,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
kamalesh@linux.vnet.ibm.com, pmladek@suse.com, jeyu@redhat.com,
live-patching@vger.kernel.org
Subject: Re: [PATCH 0/5] Live patching for powerpc
Date: Fri, 15 Apr 2016 07:59:39 -0500 [thread overview]
Message-ID: <20160415125939.lrft3nawlzuozjkb@treble> (raw)
In-Reply-To: <1460719369.22415.1.camel@ellerman.id.au>
On Fri, Apr 15, 2016 at 09:22:49PM +1000, Michael Ellerman wrote:
> On Thu, 2016-04-14 at 11:41 -0500, Josh Poimboeuf wrote:
> > On Thu, Apr 14, 2016 at 05:20:29PM +0200, Torsten Duwe wrote:
> > > On Thu, Apr 14, 2016 at 11:08:02PM +1000, Michael Ellerman wrote:
> > > > On Thu, 2016-04-14 at 14:57 +0200, Torsten Duwe wrote:
> > > > > FTR: then I still have a few ppc64 hunks floating around to support certain consistency
> > > > > models...
> > > >
> > > > OK. I'm not quite sure what you mean but post them and we'll see I guess :)
> > >
> > > It's *roughly* the ppc64 equivalent of Josh Poimboeuf's Mar 25
>
> > > > [RFC PATCH v1.9 14/14] livepatch: update task universe when exiting kernel
> > > which only considers x86.
> > >
> > > It's forward ported from an earlier code base; there's some glue missing,
> > > but here it is, for reference.
> > >
> > > Signed-off-by: Torsten Duwe <duwe@suse.de>
> >
> > Hi Torsten,
> >
> > Thanks for sharing. This is quite fortuitous as Miroslav just today
> > mentioned to me that we would need something like this. If you don't
> > mind, I may pull this patch or some variant of it into v2 of the
> > consistency model.
>
> Well please wait for me to review & ack it before you pull it into anything
> permanent.
>
> At a quick glance it seems OK but I'd probably do it a little differently. I'll
> try and have a closer look next week.
Sure, no problem. The consistency model patches are still in
development so they won't be merged anytime soon. And we wouldn't merge
any powerpc code without maintainer acks anyway. I'm just glad you guys
are looking at it so I don't have to butcher it ;-)
--
Josh
next prev parent reply other threads:[~2016-04-15 12:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 12:53 Michael Ellerman
2016-04-13 12:53 ` [PATCH 1/5] ftrace: Make ftrace_location_range() global Michael Ellerman
2016-04-19 10:16 ` [1/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 2/5] livepatch: Allow architectures to specify an alternate ftrace location Michael Ellerman
2016-04-14 12:01 ` Miroslav Benes
2016-04-14 13:06 ` Michael Ellerman
2016-04-14 14:06 ` Miroslav Benes
2016-04-19 10:16 ` [2/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 3/5] powerpc/livepatch: Add livepatch header Michael Ellerman
2016-04-14 12:18 ` Miroslav Benes
2016-04-14 12:23 ` Miroslav Benes
2016-04-14 13:12 ` Michael Ellerman
2016-04-19 10:16 ` [3/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 4/5] powerpc/livepatch: Add livepatch stack to struct thread_info Michael Ellerman
2016-04-19 10:16 ` [4/5] " Michael Ellerman
2016-04-13 12:53 ` [PATCH 5/5] powerpc/livepatch: Add live patching support on ppc64le Michael Ellerman
2016-04-19 10:16 ` [5/5] " Michael Ellerman
2016-04-13 13:01 ` [PATCH 0/5] Live patching for powerpc Miroslav Benes
2016-04-13 13:22 ` Jiri Kosina
2016-04-14 6:49 ` Michael Ellerman
2016-04-14 12:57 ` Torsten Duwe
2016-04-14 13:08 ` Michael Ellerman
2016-04-14 15:20 ` Torsten Duwe
2016-04-14 16:41 ` Josh Poimboeuf
2016-04-15 11:22 ` Michael Ellerman
2016-04-15 12:59 ` Josh Poimboeuf [this message]
2016-04-15 13:21 ` Michael Ellerman
2016-04-14 14:34 ` Jiri Kosina
2016-04-15 12:24 ` Michael Ellerman
2016-04-15 15:07 ` Jiri Kosina
2016-04-19 21:42 ` Balbir Singh
2016-04-19 21:52 ` Jiri Kosina
2016-04-13 18:22 ` Jessica Yu
2016-04-14 13:28 ` Miroslav Benes
2016-04-14 19:20 ` Jessica Yu
2016-04-15 8:28 ` Miroslav Benes
2016-04-15 10:01 ` 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=20160415125939.lrft3nawlzuozjkb@treble \
--to=jpoimboe@redhat.com \
--cc=bsingharora@gmail.com \
--cc=duwe@lst.de \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®