Em Thu, Oct 03, 2013 at 08:25:05AM +0200, Ingo Molnar escreveu:
> * Ramkumar Ramachandra wrote:
> > David Ahern wrote:
> > > If you trust your users make the debugfs mount point rx by group,world.
> > Thanks David. I can preserve this configuration across reboots by
> > putting an entry in
* Ramkumar Ramachandra wrote:
> Ingo Molnar wrote:
> >echo 'kernel.perf_event_paranoid = -1' >> /etc/sysctl.conf
>
> Thanks Ingo. It's called /etc/sysctl.d/* now:
> https://www.archlinux.org/news/deprecation-of-etcsysctlconf/
That works too, on modern distros.
Thanks,
Ingo
--
To
Ingo Molnar wrote:
>echo 'kernel.perf_event_paranoid = -1' >> /etc/sysctl.conf
Thanks Ingo. It's called /etc/sysctl.d/* now:
https://www.archlinux.org/news/deprecation-of-etcsysctlconf/
> The current output:
>
> comet:~/tip> perf trace
> Couldn't read the raw_syscalls tracepoints
* Ramkumar Ramachandra wrote:
> David Ahern wrote:
> > If you trust your users make the debugfs mount point rx by group,world.
>
> Thanks David. I can preserve this configuration across reboots by
> putting an entry in fstab, right? How do I preserve the value of
>
* Ramkumar Ramachandra artag...@gmail.com wrote:
David Ahern wrote:
If you trust your users make the debugfs mount point rx by group,world.
Thanks David. I can preserve this configuration across reboots by
putting an entry in fstab, right? How do I preserve the value of
Ingo Molnar wrote:
echo 'kernel.perf_event_paranoid = -1' /etc/sysctl.conf
Thanks Ingo. It's called /etc/sysctl.d/* now:
https://www.archlinux.org/news/deprecation-of-etcsysctlconf/
The current output:
comet:~/tip perf trace
Couldn't read the raw_syscalls tracepoints information!
* Ramkumar Ramachandra artag...@gmail.com wrote:
Ingo Molnar wrote:
echo 'kernel.perf_event_paranoid = -1' /etc/sysctl.conf
Thanks Ingo. It's called /etc/sysctl.d/* now:
https://www.archlinux.org/news/deprecation-of-etcsysctlconf/
That works too, on modern distros.
Thanks,
Em Thu, Oct 03, 2013 at 08:25:05AM +0200, Ingo Molnar escreveu:
* Ramkumar Ramachandra artag...@gmail.com wrote:
David Ahern wrote:
If you trust your users make the debugfs mount point rx by group,world.
Thanks David. I can preserve this configuration across reboots by
putting an entry
David Ahern wrote:
> If you trust your users make the debugfs mount point rx by group,world.
Thanks David. I can preserve this configuration across reboots by
putting an entry in fstab, right? How do I preserve the value of
/proc/sys/kernel/perf_event_paranoid across reboots?
--
To unsubscribe
On 10/2/13 3:20 AM, Ramkumar Ramachandra wrote:
Hi,
All the other perf tooling can be used as a normal user. At one point,
I had to touch /proc/sys/kernel/perf_event_paranoid to get me numbers
on a PMU event without a symbolic name, but that's about it.
perf-trace seems to be the exception
Hi,
All the other perf tooling can be used as a normal user. At one point,
I had to touch /proc/sys/kernel/perf_event_paranoid to get me numbers
on a PMU event without a symbolic name, but that's about it.
perf-trace seems to be the exception though:
artagnon|perf-core=:~/src/linux/tools/perf$
Hi,
All the other perf tooling can be used as a normal user. At one point,
I had to touch /proc/sys/kernel/perf_event_paranoid to get me numbers
on a PMU event without a symbolic name, but that's about it.
perf-trace seems to be the exception though:
artagnon|perf-core=:~/src/linux/tools/perf$
On 10/2/13 3:20 AM, Ramkumar Ramachandra wrote:
Hi,
All the other perf tooling can be used as a normal user. At one point,
I had to touch /proc/sys/kernel/perf_event_paranoid to get me numbers
on a PMU event without a symbolic name, but that's about it.
perf-trace seems to be the exception
David Ahern wrote:
If you trust your users make the debugfs mount point rx by group,world.
Thanks David. I can preserve this configuration across reboots by
putting an entry in fstab, right? How do I preserve the value of
/proc/sys/kernel/perf_event_paranoid across reboots?
--
To unsubscribe
14 matches
Mail list logo