[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141106144926.01441bdc@gandalf.local.home>
Date: Thu, 6 Nov 2014 14:49:26 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Josh Poimboeuf <jpoimboe@...hat.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Vojtech Pavlik <vojtech@...e.cz>,
Seth Jennings <sjenning@...hat.com>,
Jiri Kosina <jkosina@...e.cz>, live-patching@...r.kernel.org,
kpatch@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Kernel Live Patching
On Thu, 6 Nov 2014 13:34:33 -0600
Josh Poimboeuf <jpoimboe@...hat.com> wrote:
> On Thu, Nov 06, 2014 at 10:58:57AM -0800, Christoph Hellwig wrote:
> > On Thu, Nov 06, 2014 at 07:51:57PM +0100, Vojtech Pavlik wrote:
> > > I don't think this specific example was generated.
>
> So there are two ways to use this live patching API: using a generated
> module (e.g., using the kpatch-build tool) or manually compiling a
> module via kbuild.
>
> Vojtech's right, the provided example was not generated. Maybe it
> belongs in samples/livepatch?
>
I understand that there is two methods in doing this. Is it possible to
create a "simple generator" that only does the simple case. Perhaps can
detect non simple cases where it rejects the change and tells the user
they need to reboot.
Something that isn't really related to either kpatch or kGraft, but can
be used for testing purposes?
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists