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
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
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
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
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
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.
Signed-off-by: Matt Mullins
Cc: Vinson Lee
---
tools/perf/util/machine.c | 28 ++-
6 matches
Mail list logo