Stephane Eranian <eran...@google.com> writes: >> > I don't understand why this need to be so complicated. > Maybe just change the error code in case of group > overcommitment? That way, the tool could distinguish > and report the appropriate error message.
The existing errno is an ABI. Also that would handle this case, but there are a bazillion other failure cases in perf. And we can't invent new errnos for all of them. A string error interface would cover it all. Usually when something strange like this happens in perf I have to apply this patch https://lkml.org/lkml/2013/3/8/432 and use ftrace to trace it down. -Andi -- a...@linux.intel.com -- Speaking for myself only -- 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/
