> > You need to put the spinlock in for every other use of the chip
>
> I can't control somebody else's use of `hwclock` or even some future
> kernel module.
You'll have to
> What I do is have a daemon which wakes up at 1 second intervals
> and writes 'time_t' to a spare group of CMOS registers and then
> re-checksums the CMOS. If the normal shutdown occurs, this value
> is set to 0L and the CMOS is re-checksummed.
and if it isnt the machine will hang on boot with a hit F1 to continue ?
> It is 'impressive' to hit the power switch of a server and, upon
> reboot, see the actual time at which the power was lost in a log
> file.
>
> Oct 12 10:35:29 chaos monitor[11]: Power failure
Why not use the DMI BIOS interfaces from the boot loader. On a lot of boxes
DMI will tell you why the box failed
> the RTC interrupt enabled for time-keeping. Since I can't control
> all the applications that a user might run on this server, I need
> to disable all access to that chip during the time that I am
> using it.
Only the kernel can access it so who cares about other stuff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 23 2000 - 21:00:13 EST