On 08/09/2016 03:05 PM, Steven Rostedt wrote: > If an arch supports counting of SMIs (like newer intel chips do), then it > can implement arch_smi_count() to return the number of SMIs that were > triggered. The hwlat detector will call this function to get the current > number of SMIs, and then after a period, it will read that function again, > and if there's a difference, it will record that into the sample. > > For example: > > [99] inner:13 outer:16 ts:1470352534.886878855 > [100] inner:14 outer:18747 ts:1470352538.917966818 smi-count:2 > [101] inner:0 outer:19162 ts:1470352539.920988709 smi-count:6 > [102] inner:19376 outer:19276 ts:1470352540.923010578 smi-count:6 > [103] inner:19650 outer:20665 ts:1470352541.926032469 smi-count:6 > [104] inner:20526 outer:20680 ts:1470352542.973055312 smi-count:6 > [105] inner:17 outer:17 ts:1470352543.990077507 > > Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx> It worked fine in a system that I can manually cause SMIs (by turning keyboard's backlight on and off). Tested-by: Daniel Bristot de Oliveira <bristot@xxxxxxxxxx> -- Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html