mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeffrey Brian Arnold <jbarnold@MIT.EDU>
To: linux-kernel@vger.kernel.org
Cc: Tim Abbott <tabbott@MIT.EDU>, Anders Kaseorg <andersk@MIT.EDU>,
	Waseem Daher <wdaher@MIT.EDU>,
	Denys Vlasenko <vda.linux@googlemail.com>
Subject: [RFC PATCH 0/9] Ksplice: Rebootless kernel updates
Date: Sat, 13 Sep 2008 00:49:46 -0400	[thread overview]
Message-ID: <1221281397-7045-1-git-send-email-jbarnold@mit.edu> (raw)

These RFC patches add support for Ksplice [1], a rebootless update system, 
to the kernel.  I previously mentioned Ksplice to the LKML a few months 
ago [2].  The basic idea is that Ksplice can apply an update to a running 
Linux kernel based only on a source code patch and the original kernel 
source.  The Ksplice technical overview document [3] describes the design 
of Ksplice and one of the ways that Ksplice has been evaluated.

[1] http://web.mit.edu/ksplice
[2] http://lkml.org/lkml/2008/4/23/330
[3] http://web.mit.edu/ksplice/doc/ksplice.pdf

The interface between the Ksplice kernel component and the userspace 
utilities is documented in patch 6/9 of this series.  The current 
implementation of the userspace utilities is available from the Ksplice 
website and the Ksplice git repository [4].  The Ksplice userspace 
utilities transparently support both "integrated" operation (updating a 
kernel patched with this patch series) and "standalone" operation 
(updating a completely unmodified kernel).

[4] http://web.mit.edu/ksplice/ksplice.git

This series of patches depends upon the -ffunction-sections and 
-fdata-sections patches proposed by Denys Vlasenko (for reasons unrelated 
to Ksplice) a few weeks ago [5].  Ksplice's 'run-pre matching' process is 
much simpler if the original kernel was compiled with -ffunction-sections 
and -fdata-sections, and so we require these compiler options for this 
patch series.  We think that requiring these options in order to build a 
kernel with integrated Ksplice support is reasonable, but we welcome 
feedback.

[5] http://lkml.org/lkml/2008/8/24/159

Denys Vlasenko has already submitted patches to the LKML for allowing all 
architectures to compile with -ffunction-sections and -fdata-sections [5]; 
he has said that he will later submit patches making it possible to run a 
kernel with these options [6].  In the meantime, we have a patch that 
creates a CONFIG_FUNCTION_DATA_SECTIONS option for x86 and ARM [7], but we 
have not polished this patch since Denys Vlasenko is already preparing a 
similar change.

[6] http://lkml.org/lkml/2008/8/26/288
[7] http://web.mit.edu/ksplice/tmp/function-data-sections.patch

We're open to suggestions and are available to make whatever changes 
people would like to see.  (Also, I'll be at the Plumbers Conference next 
week and would be happy to chat with anyone about Ksplice in person).

Jeff Arnold
jbarnold@mit.edu

--

Documentation/ksplice.txt      |  247 +++++
MAINTAINERS                    |   10 +
arch/Kconfig                   |   14 +
arch/arm/Kconfig               |    1 +
arch/arm/kernel/ksplice-arch.c |   79 ++
arch/x86/Kconfig               |    1 +
arch/x86/kernel/ksplice-arch.c |   91 ++
arch/x86/mm/init_32.c          |    7 +-
arch/x86/mm/init_64.c          |    5 +-
include/linux/kallsyms.h       |   13 +
include/linux/ksplice.h        |  202 ++++
include/linux/module.h         |   27 +
kernel/Makefile                |    2 +
kernel/kallsyms.c              |   19 +
kernel/ksplice.c               | 1997 ++++++++++++++++++++++++++++++++++++++++
kernel/module.c                |  144 ++-
kernel/sched.c                 |    1 +
17 files changed, 2810 insertions(+), 50 deletions(-)

             reply	other threads:[~2008-09-13  4:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-13  4:49 Jeffrey Brian Arnold [this message]
2008-09-13  4:49 ` [RFC PATCH 1/9] Ksplice: Make find_symbol return a struct kernel_symbol Jeffrey Brian Arnold
2008-09-13  4:49   ` [RFC PATCH 2/9] Ksplice: Add module_data_address (the analogue of module_text_address) Jeffrey Brian Arnold
2008-09-13  4:49     ` [RFC PATCH 3/9] Ksplice: Add functions for walking kallsyms symbols Jeffrey Brian Arnold
2008-09-13  4:49       ` [RFC PATCH 4/9] Ksplice: Make needed symbol and module functions global Jeffrey Brian Arnold
2008-09-13  4:49         ` [RFC PATCH 5/9] Ksplice: Architecture-independent core Jeffrey Brian Arnold
     [not found]           ` <8d86b7714a1012014ce3533aa24dc88704fe14a6.1221271644.git.jbarnold@mit.edu>
2008-09-13  4:49             ` [RFC PATCH 5/9] Ksplice core (architecture independent) Jeffrey Brian Arnold
2008-09-13  4:49               ` [RFC PATCH 6/9] Ksplice: Documentation Jeffrey Brian Arnold
2008-09-13  4:49             ` [RFC PATCH 6/9] Ksplice documentation Jeffrey Brian Arnold
2008-09-13  4:49               ` [RFC PATCH 7/9] Ksplice: x86-32 and x86-64 support Jeffrey Brian Arnold
2008-09-13  4:49                 ` [RFC PATCH 8/9] Ksplice: ARM support Jeffrey Brian Arnold
2008-09-13  4:49                   ` [RFC PATCH 9/9] Ksplice: Add support for building Ksplice as a module Jeffrey Brian Arnold
2008-09-13  5:12 ` [RFC PATCH 0/9] Ksplice: Rebootless kernel updates Alexey Dobriyan
2008-09-14 20:24   ` Jeff Arnold

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=1221281397-7045-1-git-send-email-jbarnold@mit.edu \
    --to=jbarnold@mit.edu \
    --cc=andersk@MIT.EDU \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tabbott@MIT.EDU \
    --cc=vda.linux@googlemail.com \
    --cc=wdaher@MIT.EDU \
    /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®