The key here is that supported environments are listed out in detail in the product release notes. Intel THOROUGHLY tests VTune in those specific environments, which is why we urge users to stick to them.
If you're exploring newterritory, the software may or may not work --like every application on the planet: surely we can agree this is not a VTune-specific quirk. Applications always list the environments that they can be expected to work in, and VTune is no exception.
The known and unknown variations out in the market over the past 5 years say, of and withinOS distributions -- kernel, glibc, glibc++, etc etc etc --mixed with the released processors at the time would create a staggeringly large test and support matrix, most of which would likely not even be of interest to our user base. That's why we target specific distributions, and also why our support of newer releases takes some time.
Occasionally our customers are interested in the newer OS environments, or sometimes less popular ones, before we are able to update our software to accomodate them. Since the remote agent (vtserver) is a lean, mean profiling machine, typically it supports new environments before vtl/vtlec does.
One of the important functions of this forum is to help Intel hear when we're missing the mark, and conversations like this threadare SUPER important to us towards learning how we can do better.
jdg
Message Edited by jdgallag on 06-11-2005 10:12 AM
Message Edited by jdgallag on 06-11-2005 10:27 AM
