<[email protected]> writes:
> 2) Dell OpenManage
> The main use of this driver by openmanage will be to read the System
> Event Log that BIOS keeps. Here are some other random relevant points:
Are there machine check events from the last boot in that event log?
If yes it would be extremly cool to feed this data into mcelog
using the /dev/mcelog device after boot up. It probably would
need a few functions in exported in arch/x86_64/kernel/mce.c,
but I would be fine with that. The advantage would be that
all machine checks would be in a common log and can be easily
analyzed by higher level infrastructure (like a cluster manager)
The code used to dump the MCEs from the hardware registers left over
at boot, but so many BIOS keep bogus data in there that this had to be
turned off.
Only tricky part might be to make sure this data is not logged
twice.
I think it would be better to do this in kernel space if it's
simple enough. In theory mcelog could get a write method too
so that user space could inject events, but that would
have the disadvantage that everybody distribution would need
a magic Dell specific program to just do that. In the kernel it would just
work transparently.
/dev/mcelog only exists on x86-64 right now, but will
probably appear on i386 at some point too.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |