Re: [PATCH] perf tools: get version from uname(2), not /proc

2015-10-07 Thread Adrian Hunter
On 07/10/15 20:11, Matt Mullins wrote: > On Wed, Oct 07, 2015 at 11:19:17AM +0300, Adrian Hunter wrote: >> On 07/10/15 11:18, Jiri Olsa wrote: >>> On Tue, Oct 06, 2015 at 03:53:14PM -0700, Matt Mullins wrote: Tools in kmod (e.g. modprobe) compose the module path from the release from unam

Re: [PATCH] perf tools: get version from uname(2), not /proc

2015-10-07 Thread Matt Mullins
On Wed, Oct 07, 2015 at 11:19:17AM +0300, Adrian Hunter wrote: > On 07/10/15 11:18, Jiri Olsa wrote: > > On Tue, Oct 06, 2015 at 03:53:14PM -0700, Matt Mullins wrote: > >> Tools in kmod (e.g. modprobe) compose the module path from the release > >> from uname(2). Because we use the UNAME26 personal

Re: [PATCH] perf tools: get version from uname(2), not /proc

2015-10-07 Thread Andi Kleen
On Tue, Oct 06, 2015 at 03:53:14PM -0700, Matt Mullins wrote: > Tools in kmod (e.g. modprobe) compose the module path from the release > from uname(2). Because we use the UNAME26 personality, we need perf to > find modules located at the same path as the system tools. May be easier to just reset

Re: [PATCH] perf tools: get version from uname(2), not /proc

2015-10-07 Thread Adrian Hunter
On 07/10/15 11:18, Jiri Olsa wrote: > On Tue, Oct 06, 2015 at 03:53:14PM -0700, Matt Mullins wrote: >> Tools in kmod (e.g. modprobe) compose the module path from the release >> from uname(2). Because we use the UNAME26 personality, we need perf to >> find modules located at the same path as the sy

Re: [PATCH] perf tools: get version from uname(2), not /proc

2015-10-07 Thread Jiri Olsa
On Tue, Oct 06, 2015 at 03:53:14PM -0700, Matt Mullins wrote: > Tools in kmod (e.g. modprobe) compose the module path from the release > from uname(2). Because we use the UNAME26 personality, we need perf to > find modules located at the same path as the system tools. I guess it's easy to google