Software Tuning, Performance Optimization & Platform Monitoring
Discussion around monitoring and software tuning methodologies, Performance Monitoring Unit (PMU) of Intel microprocessors, and platform monitoring
Announcements
Intel Customer Support will be observing the Martin Luther King holiday on Monday, Jan. 17, and will return on Tues. Jan. 18.
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646

";" is missing in CSV output of pcm.x

Hidekatsu_Imura
Beginner
129 Views

It seems ";" is missing after core L2CLK value in csv output.
Could you check below?

------- pcm.cpp-------

        for (uint32 i = 0; i < m->getNumCores(); ++i)
        {
            if (cpu_model != PCM::ATOM)
                {
                    cout << getExecUsage(cstates1, cstates2) <<
                    ';' << getIPC(cstates1, cstates2) <<
                    ';' << getRelativeFrequency(cstates1, cstates2) <<
                    ';' << getActiveRelativeFrequency(cstates1, cstates2) <<
                    ';' << float_format(getL3CacheMisses(cstates1, cstates2)) <<
                    ';' << float_format(getL2CacheMisses(cstates1, cstates2)) <<
                    ';' << getL3CacheHitRatio(cstates1, cstates2) <<
                    ';' << getL2CacheHitRatio(cstates1, cstates2) <<
                    ';' << getCyclesLostDueL3CacheMisses(cstates1, cstates2) <<
                    ';' << getCyclesLostDueL2CacheMisses(cstates1, cstates2) ;
                                                                                                                             // <---- "<<;" is missing here

                    if (m->L3CacheOccupancyMetricAvailable())
                        cout << ';' << l3cache_occ_format(getL3CacheOccupancy(cstates2)) ;
                }

 

 

 

0 Kudos
2 Replies
Otto_B_Intel
Employee
129 Views

Sounds plausible, i would probably put the cout << ":" at the end of the loop to avoid the same issue for the L3CacheOccupancy.

Otto_B_Intel
Employee
129 Views

It looks likes it is already fixed in the internal version, but i don't know when there will be a release with this fix included. Thanks for the report! 

Reply