[PATCH] 2.6 PPC64: Reduce rtas spamming
Nathan Fontenot
nfont at austin.ibm.com
Thu Jul 22 08:23:17 EST 2004
Dave Hansen wrote:
> As for the other things in that directory, could you do an ls on your
> system and describe which ones you think need to be kept?
>
> -- Dave
Here we go...
# ls /proc/ppc64/rtas
. clock frequency progress rtasmsgs volume
.. error_log poweron rmo_buffer sensors
With the addition of rmo_buffer you can make rtas calls from user space.
Thus we may be able to get rid of the following items.
o clock - get/set platform time.
o frequency - set the frequency of the system speaker.
o progress - read/write data to the system led display
o volume - set the volume of the system speaker.
o power_on - set a future poweron time for the system
The remaining should be retained
o rtasmsgs - turn on/off rtas event messages to /var/log/message.
o error_log - rtas_errd uses this to get rtas events from the kernel.
o rmo_buffer - get a rmo region to make rtas calls from user space.
o sensors - displays the surrent state of system sensors
All of theses are defined in arch/ppc64/kernel/rtas-proc.c, except for
error_log which is in arch/ppc64/kernel/rtasd.c if anyone cares to look.
Nathan F.
** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/
More information about the Linuxppc64-dev
mailing list