On Wed, 2009-07-01 at 02:12 +0800, Anthony Liguori wrote: > Hi Huang, > > Huang Ying wrote: > > - MCE features are initialized when VCPU is intialized according to CPUID. > > - A monitor command "mce" is added to inject a MCE. > > - A new interrupt mask: CPU_INTERRUPT_MCE is added to inject the MCE. > > > > Can you post some instructions on how to test this functionality? During development, I use QEMU monitor command "mce" to test this functionality. For corrected error, you can use /sbin/mcelog to get the error information. For uncorrected error, you will get panic. If you want to get result faster for corrected error, set the following sysfs file to a small number, which is seconds between corrected error polls. /sys/devices/system/machinecheck/machinecheck0/check_interval For corrected error: mce 0 1 0x8000000000000000 0x0 0x0 0x0 For uncorrected error: mce 0 1 0xb200000000000000 0x0 0x0 0x0 > For > instance, I believe Linux is capable of delivering a SIGBUS to a process > based on certain MCE's. I'm not sure what the steps would be though to > create a process using a particular physical memory address, generate a > MCE for that address, and then inspect that the process received the signal. > > Are you testing the patches via something like that? It is possible to test like that, but I think it is much easier to test the case I mentioned above. Best Regards, Huang Ying -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
