On Fri, Jun 23, 2017 at 11:27:25AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jun 23, 2017 at 02:48:23PM +0900, Namhyung Kim escreveu:
> > When /proc/kallsyms is used for kernel address, addresses in module can
> > be changed when the module is reloaded. So if one did perf record with
> >
On Fri, Jun 23, 2017 at 11:27:25AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jun 23, 2017 at 02:48:23PM +0900, Namhyung Kim escreveu:
> > When /proc/kallsyms is used for kernel address, addresses in module can
> > be changed when the module is reloaded. So if one did perf record with
> >
Em Fri, Jun 23, 2017 at 02:48:23PM +0900, Namhyung Kim escreveu:
> When /proc/kallsyms is used for kernel address, addresses in module can
> be changed when the module is reloaded. So if one did perf record with
> some module and then for some reason reload the module. Then perf
> report might
Em Fri, Jun 23, 2017 at 02:48:23PM +0900, Namhyung Kim escreveu:
> When /proc/kallsyms is used for kernel address, addresses in module can
> be changed when the module is reloaded. So if one did perf record with
> some module and then for some reason reload the module. Then perf
> report might
When /proc/kallsyms is used for kernel address, addresses in module can
be changed when the module is reloaded. So if one did perf record with
some module and then for some reason reload the module. Then perf
report might see a different address for the module and the output can
show incorrect
When /proc/kallsyms is used for kernel address, addresses in module can
be changed when the module is reloaded. So if one did perf record with
some module and then for some reason reload the module. Then perf
report might see a different address for the module and the output can
show incorrect
6 matches
Mail list logo