* Fast shutdown
@ 2002-11-12 15:04 GOTZON ASTONDOA
2002-11-15 21:10 ` William A. Gatliff
0 siblings, 1 reply; 3+ messages in thread
From: GOTZON ASTONDOA @ 2002-11-12 15:04 UTC (permalink / raw)
To: linuxppc-embedded
Hi all:
Our custom board has to microprocessors: 68K and PowerPC. We have
instaled Linux in the PowerPc side.
When the user suddenly shutdowns the board, the 68K sends an
interrupt to the PowerPC.We have more or less 8 mSeg to close all the Linux
system (it has hard disk, ethernet, ftp and our own application).
Can somebody tell me any idea to close the Linux system in the
fastest way? We are thinking in capture the interrupt signal, but, is it
enough fast?
Thanks for your help in advance.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Fast shutdown
2002-11-12 15:04 Fast shutdown GOTZON ASTONDOA
@ 2002-11-15 21:10 ` William A. Gatliff
2002-11-22 8:04 ` Amit Chaudhary
0 siblings, 1 reply; 3+ messages in thread
From: William A. Gatliff @ 2002-11-15 21:10 UTC (permalink / raw)
To: GOTZON ASTONDOA; +Cc: linuxppc-embedded
On Tue, Nov 12, 2002 at 04:04:39PM +0100, GOTZON ASTONDOA wrote:
>
> Hi all:
>
> Our custom board has to microprocessors: 68K and PowerPC. We have
> instaled Linux in the PowerPc side.
> When the user suddenly shutdowns the board, the 68K sends an
> interrupt to the PowerPC.We have more or less 8 mSeg to close all the Linux
> system (it has hard disk, ethernet, ftp and our own application).
>
> Can somebody tell me any idea to close the Linux system in the
> fastest way? We are thinking in capture the interrupt signal, but, is it
> enough fast?
You'll probably want to dump /sbin/init, at least.
Just throwing something out for starters....
You could have an interrupt handler watching the signal from the 68k,
and sending a message via named pipe (perhaps) to a userspace program.
The userspace program would signal all your other programs, sync(),
then wait for powerdown.
I think you'll want all your processes doing synchronous i/o, so that
you don't have much in the way of unwritten disk data to worry with.
You'll probably also want a journaled filesystem, for those times when
8ms just isn't enough...
Hope this gives you a good starting point,
b.g.
--
Bill Gatliff
Embedded systems and Free Software. Yea, it *is* all that!
See http://billgatliff.com for details.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Fast shutdown
2002-11-15 21:10 ` William A. Gatliff
@ 2002-11-22 8:04 ` Amit Chaudhary
0 siblings, 0 replies; 3+ messages in thread
From: Amit Chaudhary @ 2002-11-22 8:04 UTC (permalink / raw)
To: GOTZON ASTONDOA; +Cc: bgat, linuxppc-embedded
William A. Gatliff wrote:
> On Tue, Nov 12, 2002 at 04:04:39PM +0100, GOTZON ASTONDOA wrote:
> >interrupt to the PowerPC.We have more or less 8 mSeg to close all the
> Linux
> >system (it has hard disk, ethernet, ftp and our own application).
> >
> > Can somebody tell me any idea to close the Linux system in the
> >fastest way? We are thinking in capture the interrupt signal, but, is it
> >enough fast?
>
>
>
> You could have an interrupt handler watching the signal from the 68k,
> and sending a message via named pipe (perhaps) to a userspace program.
> The userspace program would signal all your other programs, sync(),
> then wait for powerdown.
Another option is mount the main fs as readonly, put in a robust
recovery for any config data fs and use something equivalent of a reboot -f.
Amit
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-11-22 8:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-11-12 15:04 Fast shutdown GOTZON ASTONDOA
2002-11-15 21:10 ` William A. Gatliff
2002-11-22 8:04 ` Amit Chaudhary
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).