From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] oprofile: 2 patches
Date: Thu, 13 Nov 2014 17:44:57 +0100 [thread overview]
Message-ID: <20141113164457.GN30196@pengutronix.de> (raw)
In-Reply-To: <1413928155-14799-1-git-send-email-post@lespocky.de>
On Tue, Oct 21, 2014 at 11:49:12PM +0200, Alexander Dahl wrote:
> 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.
I've simplified the patches by making the kernel headers mandatory.
Please test if it still works for you.
Michael
>
> Greets
> Alex
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-11-13 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 21:49 Alexander Dahl
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 ` Michael Olbrich [this message]
2014-11-14 10:06 ` [ptxdist] oprofile: 2 patches 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=20141113164457.GN30196@pengutronix.de \
--to=m.olbrich@pengutronix.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