On Mon, Mar 30, 2015 at 12:41 PM, David Ahern <dsah...@gmail.com> wrote: > On 3/30/15 1:33 PM, Peter Zijlstra wrote: >> >> On Mon, Mar 30, 2015 at 11:24:12AM -0600, David Ahern wrote: >>> >>> This works but the result is not always intuitive as to why it failed. >>> >>> On a kernel that does not support the clock id you get: >>> $ perf sched record -k mono -- sleep 1 >>> Error: >>> clockid not supported. >>> >>> And on a kernel that supports clockid but not for NMI: >>> >>> $ perf record -k realtime -a -- sleep 1 >>> Error: >>> clockid not supported. >>> >>> --> H/W counters so realtime is not allowed >>> >>> Same message though different root causes. >> >> >> Heh, ok I can fudge that :-) >> > > What about having the kernel return 'not supported' error for the latter -- > H/W counters with unsafe clock?
I have reassembled all the pieces from Peter's patch. I will post it with V6 of the JIT patches today. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
