2009/4/2 <x...@ict.ac.cn>:
>
> Yes. for example:
> pfmon -e
> L3_READS_ALL_MISS:M:E:S:I,back_end_bubble_all,be_exe_bubble_all,l2d_references_reads,L3_READS_ALL_ALL:M:E:S:I,L3_READS_ALL_HIT:M:E:S:I,L2D_OZQ_CANCELS0_FILL_ST_CONF,l1dtlb_transfer,l2dtlb_misses,dtlb_inserts_hpw,er_mem_read_out_hi,er_mem_read_out_lo
> ls
Works for me on my system.
You need to enable perfmon debugging and send me the output.
in the pfmon package, do:
pfmon/tests/pfdbg --on --printk
run test, grab syslog output.
>
> That's 12 events and I get "cannot write PMCs: Invalid argument"
> Then delete any 6 events on the event list, i.e. remain 6 events, all will
> be ok on my system.
>
>
>
>> On Thu, Apr 2, 2009 at 3:29 PM, <x...@ict.ac.cn> wrote:
>>> Hi all:
>>>
>>> Now I'm using a dual-core Itanium2 processor with perfmon kernel 2.81,
>>> pfmlib and pfmon V3.7.
>>> I have used pfmon3.2 with kernel 2.0 for long time. I updated the
>>> perfmon
>>> kernel to 2.81 recently and now I get problems. When I count for more
>>> than
>>> 6 events with pfmon, I get the error message "cannot write PMCs: Invalid
>>> argument". If the number of events is less than or equal to 6, pfmon
>>> works
>>> well.
>>
>> You need to provide the exact pfmon cmdline so I can try and reproduce the
>> problem.
>>
>>>
>>> I also get the dmessage as "perfmon: perfmon: Errata 121 PMD10/PMD15
>>> cannot be used to overflowwhen threads on on" when that error occurs.
>>>
>> That is normal. There is indeed a processor bug.
>>
>>
>>> Note that Montecito processor has 12 PMUs.
>>>
>> Yes, but there are restrictions on some events.
>>
>>
>
>
>
------------------------------------------------------------------------------
_______________________________________________
perfmon2-devel mailing list
perfmon2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
