On Sun, 25 Jan 2009, Thomas Gleixner wrote: > On Sat, 24 Jan 2009, Jon Masters wrote: > > > The only reasonable thing you can do on a SMI plagued system is to > > > identify the device which makes use of SMIs. Legacy ISA devices and > > > USB are usually good candidates. If that does not help, don't use it > > > for real-time :) > > > > Indeed. This is why I wrote an smi_detector that sits in kernel space > > and can be reasonably sure measured discrepancies are attributable to > > SMI behavior. We want to log and detect such things before RT systems > > are deployed, not have users actively trying to work around SMI overhead > > after the fact. > > Agreed. A tool to detect SMI disturbance is a good thing. It just > needs to be documented that users should take the results and talk to > their board vendor. I know that off the shelf hardware will not be > fixed, but industrial grade hardware vendors usually have an interest > to get such problems resolved. "gamer enthusiast" hardware might also get fixed. You just need two or three posts to the "enthusiasts" forums about how SMI steals CPU cycles and slow down their framerates, and suddenly, benchmarks will start going on and on about how MoBo x has a high number of SMIs per minute, where MoBo y doesn't... The people who want low-latency desktops for audio work will also pay attention to such benchmarks and will vote with their wallet. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- 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
