3 ms·
What is the use case of this tool? Debugging embedded hardware issues or something? The requirement of an kernel module raises the bar quite a bit and I don't r
by eikenberry 4y ago
What is the use case of this tool? Debugging embedded hardware issues or something? The requirement of an kernel module raises the bar quite a bit and I don't really understand the need.
- jeffbee 4y agoI don't get it either. It doesn't give more information than `turbostat` or `powertop`. In fact it gives much less information. And installing the kernel module starts timers that immediately become the main reason the system is awake and drawing power, at least on my Intel "Raptor Lake" desktop.
- thulle 4y agoThe feature to show DIMM timings seem unique, I haven't seen that before. ECC DIMMs use the same ICs as regular memory but doesn't have the XMP/EXPO overclocking profiles, so I have to manually overclock them to get performance closer to regular RAM. Being able to have my benchmark/stability-test script write down the current timings in the log instead of having to write them down as I'm setting them in BIOS and later type them in would be an improvement.
- bitcharmer 4y agoThe first thing that comes to mind when considering why this requires a form of a kernel module would be accessing functionality that normally results in protection faults, eg. trying to disable LAPIC interrupts from userspace with combination of iopl(3) and CLI instruction.