From: ebiederm@xmission.com (Eric W. Biederman)
To: Ed Tomlinson <tomlins@cam.org>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] kexec for 2.5.51....
Date: 15 Dec 2002 17:41:35 -0700 [thread overview]
Message-ID: <m1wumaaj7k.fsf@frodo.biederman.org> (raw)
In-Reply-To: <200212151641.49062.tomlins@cam.org>
Ed Tomlinson <tomlins@cam.org> writes:
> On December 15, 2002 04:03 pm, Eric W. Biederman wrote:
> > Ed Tomlinson <tomlins@cam.org> writes:
> > > Why not include this info in kexec -h ? Bet it would prevent a few
> > > failure reports...
> >
> > I will look, at that.
> >
> > > Two more possible additions to the kexec command.
> > >
> > > 1. kexec -q which returns rc=1 and types the pending selection and
> > > its command/append string if one exists and returns rc=0 if nothing
> > > is pending.
> >
> > This would require effort to little purpose. If you just call kexec
> > it loads the kernel and then calls shutdown -r now. So the loaded kernel
> > should be a transient entity anyway.
>
> Consider, you are not sure what kexec has been setup to do (maybe
> some other admin has something setup to take a crash dump etc). You
> do not want to destroy this setup, so you do kexec -q
>
> Think being able to query the pending kexec is very usefull. Also
> using an rc means that scripts can use it too.
I think setting up something like /etc/lilo.conf say /etc/kexec.conf
is probably practical. You have already seen how difficult it is to
bring up the hardware into a sane state from an arbitrary point. So
we can cross the crash dump bridge when we come to it.
If this was simply a case of supporting linux the problem would be
some easier. But I also intend to support booting other operating
systems.
Now I think there is some advantage in setting up a new set of page
tables and just switching to those at kexec time, it slightly reduces
the amount of work I need to do at kexec time, enhancing the
reliability of something like kexec on panic. And that could
probably be exported in /proc/<pid>/mem. So if and when I go this
route I will keep your request in mind.
> > > 2. kexec -c which clears any pending kernels.
> >
> > This I can and should do. The kernel side is already implemented.
Oh, and of course I accept patches so you don't have to wait for me to
implement something.
Eric
next prev parent reply other threads:[~2002-12-16 0:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-14 17:15 [PATCH] kexec for 2.5.51 Ed Tomlinson
2002-12-14 19:37 ` Eric W. Biederman
2002-12-14 23:59 ` Ed Tomlinson
2002-12-15 21:03 ` Eric W. Biederman
2002-12-15 21:41 ` Ed Tomlinson
2002-12-16 0:41 ` Eric W. Biederman [this message]
2002-12-14 19:49 ` Greg KH
[not found] ` <200212172243.52786.tomlins@cam.org>
[not found] ` <20021218054802.GF28629@kroah.com>
2003-01-13 3:42 ` usb mouse and 2.5.56bk Ed Tomlinson
2003-01-14 1:23 ` Greg KH
2003-01-14 13:44 ` Ed Tomlinson
2003-01-15 8:02 ` Greg KH
[not found] ` <mailman.1042429501.18263.linux-kernel2news@redhat.com>
2003-01-13 19:06 ` Pete Zaitcev
2003-01-13 19:26 ` Joshua M. Kwan
-- strict thread matches above, loose matches on Subject: below --
2002-12-14 8:26 [PATCH] kexec for 2.5.51 Eric W. Biederman
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=m1wumaaj7k.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomlins@cam.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;
as well as URLs for NNTP newsgroup(s).