From: Andi Kleen <andi@firstfloor.org>
To: Jeff Arnold <jbarnold@MIT.EDU>
Cc: Nikanth Karthikesan <knikanth@suse.de>,
linux-kernel@vger.kernel.org, ananth@in.ibm.com,
davem@davemloft.net, mhiramat@redhat.com, contact@ksplice.com,
jbarnold@ksplice.com, tabbott@ksplice.com, wdaher@ksplice.com,
andersk@ksplice.com
Subject: Re: [RFC] kreplace: Rebootless kernel updates
Date: Sun, 23 Nov 2008 20:39:10 +0100 [thread overview]
Message-ID: <87myfqi65d.fsf@basil.nowhere.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0811211303460.24014@vinegar-pot.mit.edu> (Jeff Arnold's message of "Fri, 21 Nov 2008 22:46:59 -0500 (EST)")
Jeff Arnold <jbarnold@MIT.EDU> writes:
> Hello,
>
>> [kreplace] is currently a x86_64 only _hack_
>
> The point of Ksplice is to be a hot update system that isn't a hack.
> Ksplice is quite far along at this point; it implements many safety and
> automation features that kreplace doesn't address. Is there something in
> particular that discouraged you from using Ksplice?
I suspect that it wasn't mainline?
The usual problem is that it's much easier to get simple patches
in than complicated ones.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-11-23 19:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 11:50 [RFC] kreplace: Rebootless kernel updates Nikanth Karthikesan
2008-11-21 13:38 ` Ananth N Mavinakayanahalli
2008-11-21 16:04 ` Balbir Singh
2008-11-21 17:29 ` Chris Friesen
2008-11-24 11:07 ` Nikanth Karthikesan
2008-11-24 11:07 ` Nikanth Karthikesan
2008-11-21 14:39 ` Masami Hiramatsu
2008-11-24 11:07 ` Nikanth Karthikesan
2008-11-24 15:15 ` Masami Hiramatsu
2008-11-26 2:48 ` Nikanth K
2008-11-21 20:19 ` Anders Kaseorg
2008-11-22 3:46 ` Jeff Arnold
2008-11-23 19:39 ` Andi Kleen [this message]
2008-11-23 20:53 ` Jeff Arnold
2008-11-24 11:07 ` Nikanth Karthikesan
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=87myfqi65d.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=ananth@in.ibm.com \
--cc=andersk@ksplice.com \
--cc=contact@ksplice.com \
--cc=davem@davemloft.net \
--cc=jbarnold@MIT.EDU \
--cc=jbarnold@ksplice.com \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.com \
--cc=tabbott@ksplice.com \
--cc=wdaher@ksplice.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