Open main menu




242 bytes added, 20:42, 12 August 2018
no edit summary
* <code>10</code>: Hardware Duty Cycling
Once the bit mask is obtained we have to walk over each bit set and call <code>cpuid_count(0xd, component, &eax, &ebx, &ecx, &edx)</code>, where <code>component</code> is the bit position we are interested in. In other words it should be from 0 to 10. The result of this call is sitting in <code>ebx</code> which represent offset of the component from the frame base address and <code>eax</code> which shows component size. Note that some of components are supervisor components and if <code>(ecx & 1) == 0</code> from the <code>cpuid_count</code> call above then its offset should not be considered while size is undefinedstill valid. === Potential memory corruption === When processes are dumped and restored on different cpu, the application may have remembered frame size on its own somewhere inside own code and in worst scenario...