Re: perf record: can I specify multiple events and use differentsample-after value

[Yuanfang Chen]

On Mon, Feb 27, 2012 at 8:56 AM, Yuanfang Chen <cyfmxc@xxxxxxxxx> wrote:
>
> On Feb 26, 2012 10:23 PM, "David Ahern" <dsahern@xxxxxxxxx> wrote:
>>
>> On 2/24/12 3:41 PM, Yuanfang Chen wrote:
>>>
>>> I think I'll settle with perf record for now. Still, unlike trace
>>> event, sample count is not meaningful for PMU event. Output of "perf
>>> script" does not include period value. One line of code will do the
>>> work.
>>>
>>> lude 17342 750118.202915: raw 0x3c: 86754 Â Â Âffffffff8115f6b9
>>> __mem_cgroup_commit_char
>>> lude 17342 750118.203025: raw 0x3c: 1027634 Â ffffffff811344b9
>>> __mem_cgroup_commit_char
>>>
>>> 86754, 1027634 is the period value. But I'm not sure which is the PMU
>>> value, is it just period value, or period x sample after. If so, what
>>> is the sample after value?
>>
>>
>> You lost me. You modified perf-script to print the period?
>>
>> Are you asking for the PMU counter value for 0x3c?

     yes

>>
>> What perf commands are you running?

    perf script
    (with no options)

>
>>
>> David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/