From: Russ Anderson <rja@efs.americas.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: purpose of modular mca recovery
Date: Tue, 09 Aug 2005 20:45:31 +0000 [thread overview]
Message-ID: <200508092045.j79KjVwv1893089@efs.americas.sgi.com> (raw)
In-Reply-To: <20050809203915.GB28917@lst.de>
Christoph Hellwig wrote:
>
> is there any reason to built this code modular? After all it would
> usually not be loaded when it was needed. Not allowing modular mca
> recovery would help greatly because it's using some symbols that we'd
> prefer to unexport before chaning some implementation details
> (tasklist_lock and maybe force_sig)
It is extremely handy for testing to be able to insmod/rmmod
mca_recovery to test changes, rather than having to reboot the
kernel. It is also a handly way to turn it on/off the recovery
code or upgrade without having to reboot.
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
next prev parent reply other threads:[~2005-08-09 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 20:39 purpose of modular mca recovery Christoph Hellwig
2005-08-09 20:45 ` Russ Anderson [this message]
2005-08-09 20:57 ` Luck, Tony
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=200508092045.j79KjVwv1893089@efs.americas.sgi.com \
--to=rja@efs.americas.sgi.com \
--cc=linux-ia64@vger.kernel.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