From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] oprofile: 2 patches
Date: Tue, 21 Oct 2014 23:49:12 +0200 [thread overview]
Message-ID: <1413928155-14799-1-git-send-email-post@lespocky.de> (raw)
Hei hei,
I use oprofile today on at91sam9 which is armv5te and came cross some
things. First is the kernel header path. In the previous version
oprofile added an additional "include" to the path so it could not
find the kernel headers. I made this dependent on the kernel-header
config, one could also just fix the path.
The second patch contains one important fix for an executable called
by opcontrol, see the comment on the patch. The other one is open for
comments. Upstream dropped support for the legacy tools and recommends
usage of operf and ocount so I added it in one patch.
Greets
Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2014-10-21 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 21:49 Alexander Dahl [this message]
2014-10-21 21:49 ` [ptxdist] [PATCH 1/2] oprofile: fix kernel header path Alexander Dahl
2014-10-21 21:49 ` [ptxdist] [PATCH 2/2] oprofile: targetinstall missing and additional binaries Alexander Dahl
2014-11-13 16:44 ` [ptxdist] oprofile: 2 patches Michael Olbrich
2014-11-14 10:06 ` Alexander Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1413928155-14799-1-git-send-email-post@lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox