There's rarely any commercial code that will trigger this bug. Most multi-threaded programming today is vastly parallel in nature, which given the nature of the description, wouldn't set it off. So I see people trying to "duplicate" the bug by attempting to load all 4 cores via Orthos (even in a VM environment) and claiming there is no bug when it passes after 24 hours. Thats a wrong way of attempting to recreate the issue. It's not creating any kind of cache thrashing at a serious level (because the general assumption for programmers just 2+ years back is that you need to avoid hitting another core's cache because it'd go through a slow bus). The issue is about multiple cores hitting and competing on the same allotment of the shared cache, not about stressing the cores in parallel.
If you want to trigger the TLB bug consistently, use software that is has large amounts of cache thrashing, generally application servers or hpc research.
As for whether or not this matters, I think this is on the order of the FDIV Pentium issue in terms of seriousness and exposure. It won't happen to the vast majority of the customer base, but is generally unacceptable in comparison to previous marketed hardware. I think its fairly asinine to think "if it doesn't happen to me, its not a problem" - it just lowers the bar for future hardware.
If you want to trigger the TLB bug consistently, use software that is has large amounts of cache thrashing, generally application servers or hpc research.
As for whether or not this matters, I think this is on the order of the FDIV Pentium issue in terms of seriousness and exposure. It won't happen to the vast majority of the customer base, but is generally unacceptable in comparison to previous marketed hardware. I think its fairly asinine to think "if it doesn't happen to me, its not a problem" - it just lowers the bar for future hardware.