I can add a lot of more complex code to hunt down and evaluate the _CST objects to figure out if any C states are defined on a system. However, the modern kernel idle handler for Intel CPUs tries to identify the CPU and decide the given C states so effectively ignores information anyway. I'm quite tempted to drop this warning as it's alarming and not giving an real information that's useful to us. I suppose if we want deeper C state checking, we should move that into the cstate test rather than overload the FADT checking.
Hi Alex,
I can add a lot of more complex code to hunt down and evaluate the _CST objects to figure out if any C states are defined on a system. However, the modern kernel idle handler for Intel CPUs tries to identify the CPU and decide the given C states so effectively ignores information anyway. I'm quite tempted to drop this warning as it's alarming and not giving an real information that's useful to us. I suppose if we want deeper C state checking, we should move that into the cstate test rather than overload the FADT checking.
Colin