Re: [Powertop] segfault on Sheevaplug (ARM Kirkwood)

Rui DaCosta <ruidc at yahoo.com>
Newsgroups dev.linux.lists.powertop
Message-ID <[email protected]>
thanks, same result:


PowerTOP v2.0 needs the kernel to support the 'perf' subsystem
as well as support for trace points in the kernel:

CONFIG_PERF_EVENTS=y 
CONFIG_PERF_COUNTERS=y
CONFIG_TRACEPOINTS=y
CONFIG_TRACING=y


Regards,

Rui



________________________________
 From: Sergey Senozhatsky <sergey.senozhatsky(a)gmail.com>
To: Rui DaCosta <ruidc(a)yahoo.com> 
Cc: Arjan van de Ven <arjan(a)linux.intel.com>; Chris Ferron <chris.e.ferron(a)linux.intel.com>; "powertop(a)lists.01.org" <powertop(a)lists.01.org> 
Sent: Monday, 21 May 2012, 0:17
Subject: Re: [Powertop] segfault on Sheevaplug (ARM Kirkwood)
 
On (05/20/12 12:32), Rui DaCosta wrote:
> 
>    it was pointed out to me that  CONFIG_PERF_COUNTERS has been superseded by
>    PERF_EVENTS since 2.6.32  - see bottom section of
>    http://cateee.net/lkddb/web-lkddb/PERF_COUNTERS.html
>    so is  CONFIG_PERF_COUNTERS really required?
> 

Could you please try the following patch?

---

src/perf/perf.cpp |    3 +++
1 file changed, 3 insertions(+)

diff --git a/src/perf/perf.cpp b/src/perf/perf.cpp
index ce9ae6a..09ca390 100644
--- a/src/perf/perf.cpp
+++ b/src/perf/perf.cpp
@@ -48,6 +48,9 @@
#ifdef __alpha__
#include <asm-generic/unistd.h>
#endif
+#ifdef __arm__
+#include <asm-generic/unistd.h>
+#endif

#include "perf.h"
#include "../lib.h"
attachment.html (text/html, 2.4 KB)
<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>thanks, same result:</span></div><div><span><br></span></div><div><span>PowerTOP v2.0 needs the kernel to support the 'perf' subsystem<br>as well as support for trace points in the kernel:<br><br>CONFIG_PERF_EVENTS=y <br>CONFIG_PERF_COUNTERS=y<br>CONFIG_TRACEPOINTS=y<br>CONFIG_TRACING=y<br></span></div><div><span><br></span></div><div><span>Regards,<br></span></div><div><span>Rui<br></span></div><div><br></div>  <div style="font-size: 12pt; font-family: &quot;times new roman&quot;, &quot;new york&quot;, &quot;times&quot;, serif"> <div style="font-size: 12pt; font-family: &quot;times new roman&quot;, &quot;new york&quot;, &quot;times&quot;, serif"> <div dir="ltr"> <font size="2" face="Arial"> <hr size="1">  <b><span style="font-weight:bold;">From:</span></b> Sergey Senozhatsky &lt;[email protected]&gt;<br>
 <b><span style="font-weight: bold;">To:</span></b> Rui DaCosta &lt;[email protected]&gt; <br><b><span style="font-weight: bold;">Cc:</span></b> Arjan van de Ven &lt;[email protected]&gt;; Chris Ferron &lt;[email protected]&gt;; "[email protected]" &lt;[email protected]&gt; <br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, 21 May 2012, 0:17<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [Powertop] segfault on Sheevaplug (ARM Kirkwood)<br> </font> </div> <br>On (05/20/12 12:32), Rui DaCosta wrote:<br>&gt; <br>&gt;&nbsp; &nbsp; it was pointed out to me that&nbsp; CONFIG_PERF_COUNTERS has been superseded by<br>&gt;&nbsp; &nbsp; PERF_EVENTS since 2.6.32 &nbsp;- see bottom section of<br>&gt;&nbsp; &nbsp; <a href="http://cateee.net/lkddb/web-lkddb/PERF_COUNTERS.html" target="_blank">http://cateee.net/lkddb/web-lkddb/PERF_COUNTERS.html</a><br>&gt;&nbsp; &nbsp; so is&nbsp; CONFIG_PERF_COUNTERS really
 required?<br>&gt; <br><br>Could you please try the following patch?<br><br>---<br><br> src/perf/perf.cpp |&nbsp; &nbsp; 3 +++<br> 1 file changed, 3 insertions(+)<br><br>diff --git a/src/perf/perf.cpp b/src/perf/perf.cpp<br>index ce9ae6a..09ca390 100644<br>--- a/src/perf/perf.cpp<br>+++ b/src/perf/perf.cpp<br>@@ -48,6 +48,9 @@<br> #ifdef __alpha__<br> #include &lt;asm-generic/unistd.h&gt;<br> #endif<br>+#ifdef __arm__<br>+#include &lt;asm-generic/unistd.h&gt;<br>+#endif<br> <br> #include "perf.h"<br> #include "../lib.h"<br><br><br><br> </div> </div>  </div></body></html>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.