On Mon, Jan 26, 2009 at 9:51 AM, Jon Masters <jcm@xxxxxxxxxx> wrote: > On Sun, 2009-01-25 at 14:52 -0800, Mike Kravetz wrote: > >> Any reason why you could not do SMI detection in user level code running >> at the highest RT priority? > > Yeah. I had some suggestions about that already...the problem with that > is that you can't know whether measured latencies are due to SMIs /or/ > other kernel latencies - maybe there's a bug or other problem? I really > want to be able to say to vendors "nope, it's definitely your problem". While I agree it is tricky to sort out OS V. SMI issues it really doesn't matter if your SMI periods are less than your OS period. If you OS blocks as long as your SMI then it is hard to say for sure. One class of SMI is periodic. Looking though latency data and looking for periodic events might be handy. Say if every X seconds you experience extra latency you can pretty much bet that is an SMI. Just had an interesting idea. Why not just boot Linux as far as early console access and put the test loop in right then and there? > So I think what'll end up happening is a user process for ease of > deployment but something like smi_detector for advanced diagnostics. And > then I just hope others will write tools like the one IBM already has > that will turn off extraneous SMI generation :) I will be sending out a RFC with our implementation. On a few platforms the firmware supports turning off all "non-fatal" SMIs. There is a small driver to interface with the BIOS and some userspace bits. Thanks, Keith Mannthey LTC Real-Time -- 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
