From: Philip Balister <philip@balister.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] packagegroup-core-tools-profile.bb: Remove oprofile.
Date: Tue, 16 Jun 2015 08:33:39 -0400 [thread overview]
Message-ID: <558017A3.80707@balister.org> (raw)
In-Reply-To: <CAJTo0LYLxsH6_28DCakvnaKMpUyk=syfGcsfrQriTj8y_21n6Q@mail.gmail.com>
On 06/16/2015 08:08 AM, Burton, Ross wrote:
> On 1 June 2015 at 21:17, Philip Balister <philip@balister.org> wrote:
>
>> Oprofile functions duplicate perf. Since perf is easier to use drop
>> oprofile
>> from the core-tools-profile package.
>>
>> Also, the oprofile-ui package opens a port on the device. removing this
>> package reduces a possible security issue for devices with profiling tools.
>>
>
> I filed this in the "think about" box when you submitted it, but then
> failed to think. My concern was "oprofile is the profiling tool we support
> with oprofileui on the host" but that point is fairly moot right now as
> oprofileui doesn't work anymore... (#7054).
>
> When that's fixed, we can re-add the tooling as appropriate.
My gut feeling is people are moving to perf, which is also part of
tools-profile.
Philip
>
> Ross
>
next prev parent reply other threads:[~2015-06-16 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 20:17 [PATCH 1/2] packagegroup-core-sdk.bb: Drop distcc from the core-sdk Philip Balister
2015-06-01 20:17 ` [PATCH 2/2] packagegroup-core-tools-profile.bb: Remove oprofile Philip Balister
2015-06-16 11:33 ` Philip Balister
2015-06-16 12:08 ` Burton, Ross
2015-06-16 12:33 ` Philip Balister [this message]
2015-06-16 12:35 ` Burton, Ross
2015-06-16 11:33 ` [PATCH 1/2] packagegroup-core-sdk.bb: Drop distcc from the core-sdk Philip Balister
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=558017A3.80707@balister.org \
--to=philip@balister.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.