Prev: async: Manage execution domains
Next: sock.c: potential null dereference
From: Corey Ashford on 7 Mar 2010 18:00
On 03/07/2010 11:04 AM, Arjan van de Ven wrote:
> On Sun, 07 Mar 2010 11:01:39 -0800
> Corey Ashford<cjashfor(a)linux.vnet.ibm.com> wrote:
>>
>> I find the example given on that web page quite confusing because
>> perf currently doesn't have support for arch-dependent events like
>> that, except via "raw code" events which use the syntax -e
>> r<hex_code>. I wonder if they locally modified perf to handle those
>> events, and then forgot that they had made that modification before
>> posting up those instructions.
>
> these are just standard trace points...

Ah, I see. Thanks for the correction.

- Corey
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: async: Manage execution domains
Next: sock.c: potential null dereference