[Gc-linux-devel] Re: Problems using the new exi =?utf-8?b?ZnJhbWV3b3JrCXdpdGgJbmJk?= swap

[Albert H. <alb...@gm...>]

Daniel Thompson <daniel <at> redfelineninja.org.uk> writes:
> Agreed. After reading this I tried using another means to stress the BBA
> and therefore the EXI bus. The following command issued from the 'cube
> at my main Linux box caused a crash in less than a minute (with swap
> to /dev/aram only):
> 
> drt <at> cube:~$ ssh starfish dd if=/dev/zero > /dev/null
> 

I took a closer look to it, and it seems better than expected.

The get_rtc_time hook is not called from interrupt context, so we do not need to
protect it. It will succeed.

The set_rtc_time hook is called from user and interrupt context, depending on if
you use the /dev/rtc interface or the adjtimex syscall. The good news is that
the system is prepared for set_rtc_time to fail, so we can simply return an
error if the exi channel is busy while trying to write to the rtc.

I'll merge a patch on CVS to fix this.

Cheers,
Albert