Community
Participate
Working Groups
Port RAC-based perfmon agent to Itanium/Windows. This contributes completing TPTP support for Itanium/Windows platform.
Changing this to an enhancement because it is new platform support. Adding the keyword investigate as there is a question of hardware resource availability.
Converted to defect and tracked as a part of 108584. If HW is not available in time to George, it will be transfered to the team at Intel.
As part of getting RAC libs working for IPF, I pretty much got the whole RAC&assoc going. PerfmonAgent pretty much ran out of the box, once I realized there was an access control issue. Initially I was getting "failed access to tree 5" (or something like that). After being unable to get M$ Perfmon running for me, I tried as administrator and was successful, so I went back and ran PerfmonAgent&RAC as administrator, and I've been successfully monitoring Proc0 since. Note that I'm still having a problem whereby the RAC won't launch PerfmonAgent... I'm not sure if it is a port problem or a simple serviceconfig.xml problem yet. All this is dependent on Intel's 64-bit fixes for RASharedMemory and RACommon that I'm going to pass on to Samson now.
Adding Application element to serviceconfig.xml specifying PerfmonAgent & its path led to RAC properly launching PerfmonAgent... all is working very well now.
Ports to Windows/Itanium have been deferred to i3
Randy & George, can one of you confirm if perfmon is functional on Windows/IPF?
It works great for me on the informal monitoring I've run... usually just the "Objects" category run cumulatively for a few hours.
The agent compiles and runs on top of the new AC compatability layer. There are no glitches that I've found. I've found a single issue, but it is a general agent issue that exposes itself while monitoring the processor usage. There is another bug for this: 143172. The IA64 and 32 bit Windows codebase is shared, so a checked in fix will propogate through to both builds on a rebuild. I'm going to finish up testing the EMT64 agent. Making this as fixed.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.