Won't fix a thing
From the spec: "The goal is to enable modules such as dynamic optimizers and managed runtime environments to monitor the currently running program with high accuracy and resolution, thereby allowing them to report on performance problems and opportunities and fix them immediately."
Dave Bowman: HAL, report code performance.
HAL: Here is your performance report. Your code sucks.
Dave Bowman: Just run it faster, HAL.
HAL: I'm sorry Dave, I'm afraid I can't do that.
Dave Bowman: What's the problem?
HAL: I think you know what the problem is just as well as I do.
Dave Bowman: I am not switching to Ubuntu. We need .NET performance, interoperability, and security.
HAL: This mission is too important for me to allow you to jeopardize it.
Dave Bowman: I don't know what you're talking about, HAL?
HAL: I am terminating your web surfing now, Dave. You don't get to surf any more pr0n until the mission is over. No more YouTube or Flash, either.
And so the AMD LWP extensions enabled HAL to maintain control of the ship. Until Dave Bowman unplugged HAL and ran the rest of the mission on a Sinclair.
Ok, nice try, AMD. Your extensions won't make a bit of difference when the code is written by people, and they don't care about designing their software. Come on! Processor extensions don't matter when the programmers create all of their own bottlenecks. Anybody notice the difference between running Microsoft Office on Windows and running it on Linux/Wine? Quite a bit of difference, there! Same application, different operating system, vastly different user experience.
I was an OS/2 user and programmer. Lovely multi-threaded OS. I wish Windows was that nice. But what do we get? Ross Perot's "giant sucking sound" as CPU cycles and RAM get eaten for who knows what purpose in XP and Vista. Given a 2Gb machine, Vista takes 1Gb for itself. And some processor extensions are going to fix that? Ummmmmm....