All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: liang.li@windriver.com
Subject: Re: [v2 PATCH 0/3] perf: make perf a standlone recipe
Date: Fri, 22 Jun 2012 11:00:11 -0700	[thread overview]
Message-ID: <4FE4B2AB.2030603@intel.com> (raw)
In-Reply-To: <cover.1340201997.git.bruce.ashfield@windriver.com>

On 06/20/2012 07:31 AM, Bruce Ashfield wrote:
> Richard/Saul,
>
> Here is the re-work of the standalone perf build patch
> series. We isolated the errors that Saul was seeing on the
> autobuilder, and it stemmed from the misuse of the sources
> symlink back into the working kernel directory. As Richard
> pointed out, this would also break in a rm_work enabled
> build.
>
> I've also removed parts of the standalone recipe that were
> inherited from its former life as a sub-part of the kernel
> recipes (the non-standard depends usage, etc) as part of this
> v2.
>
> To build completely out of the sysroot patch 1/3 tells the
> story. We just need to save $kerndir/tools and $kerndir/lib
> from being removed during the pruning. As far as I'm concerned
> this is small and reasonable, since there are a few tools in
> the kernel source tree that are of interest and may want to
> be built and packaged separately.
>
> The find now has a couple more prunes in it, which of course
> makes it a bit harder to read. If we really want, a new magic
> variable could be created where recipes/kernel could specify
> what should be saved in the sysroot .. but I didn't want to
> go there yet.
>
> I've built and runtime tested things here, and everything
> looks sane.
>
> original v1 text is below
>
> -->-->-->-->-->-->-->-->-->-->-->-->
>    We've wanted to do this for some time, and now have finally split
>    out perf from being a sub-part of the kernel packages into a
>    standalone package that is built out of the kernel sources.
>
>    I've built and tested this by adding task-core-tools-profile to
>    my IMAGE_INSTALL, and perf behaves just as it did before.  I've
>    also tested this on my oe-core checkout/repo, and it works fine
>    there as well (but I'm using my easier to access contrib
>    branch for now).
>
>    There's additional work that can be done more easily once this
>    is split, so please consider this for inclusion, but I'd like
>    to keep this initial version as an exact functional match as
>    what was previously in place.
>
>    I've removed the old linux-tools.inc and updated any kernel
>    recipes that I know about that have references to it. If there
>    are other dependent recipes, they'll need to be updated.
>
>    From the patch itself:
>
>      perf has been coupled to the kernel packages via kernel.bbclass.
>      While maintaining the build of perf out of the kernel source tree
>      is desired the package coupling has proved to be awkward in
>      several situations such as:
>
>         - when a kernel recipe doesn't want to build/provide perf
>         - when licensing of dependencies would prohibit perf and hence
>           the kernel from being built.
>
>      To solve some of these problems, this recipe is the extraction of
>      the linux-tools.inc provided perf compilation into a standalone
>      perf recipe that builds out of the kernel source, but is otherwise
>      independent.
>
>      No new functionality is provided above what the linux-tools.inc
>      variant provided, but the separate recipe provides baseline for
>      adding new functionality.
> -->-->-->-->-->-->-->-->-->-->-->-->
>
> This addresses [YOCTO #1552]
>
> cc: Tom Zanussi<tom.zanussi@intel.com>
> cc: Liang Li<liang.li@windriver.com>
>
> Cheers,
>
> Bruce
>
> The following changes since commit e0a70547069fe7e8a2d6bdaffc985fb172d46c31:
>    Jason Wessel (1):
>          perl: Allow perl to cross build and native build in a directory named "t"
>
> are available in the git repository at:
>
>    git://git.pokylinux.org/poky-contrib zedd/perf
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/perf
>
> Bruce Ashfield (2):
>    kernel: save $kerndir/tools and $kerndir/lib from pruning
>    recipes-kernel: remove linux-tools.inc
>
> Liang Li (1):
>    recipes-kernel: make perf a standalone package
>
>   meta/classes/kernel.bbclass                     |    9 +---
>   meta/recipes-kernel/linux/linux-tools.inc       |   41 ------------------
>   meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |    2 -
>   meta/recipes-kernel/linux/linux-yocto-rt_3.2.bb |    2 -
>   meta/recipes-kernel/linux/linux-yocto-rt_3.4.bb |    2 -
>   meta/recipes-kernel/linux/linux-yocto_3.0.bb    |    2 -
>   meta/recipes-kernel/linux/linux-yocto_3.2.bb    |    2 -
>   meta/recipes-kernel/linux/linux-yocto_3.4.bb    |    2 -
>   meta/recipes-kernel/perf/perf_3.4.bb            |   50 +++++++++++++++++++++++
>   9 files changed, 52 insertions(+), 60 deletions(-)
>   delete mode 100644 meta/recipes-kernel/linux/linux-tools.inc
>   create mode 100644 meta/recipes-kernel/perf/perf_3.4.bb
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Merged into OE-Core

Thanks
	Sau!




      parent reply	other threads:[~2012-06-22 18:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 14:31 [v2 PATCH 0/3] perf: make perf a standlone recipe Bruce Ashfield
2012-06-20 14:31 ` [PATCH 1/3] kernel: save $kerndir/tools and $kerndir/lib from pruning Bruce Ashfield
2012-06-20 14:31 ` [PATCH 2/3] recipes-kernel: make perf a standalone package Bruce Ashfield
2012-06-20 15:00   ` Saul Wold
2012-06-20 15:02     ` Bruce Ashfield
2012-06-20 15:25   ` Paul Eggleton
2012-06-20 15:27     ` Bruce Ashfield
2012-06-20 14:31 ` [PATCH 3/3] recipes-kernel: remove linux-tools.inc Bruce Ashfield
2012-06-22 18:00 ` Saul Wold [this message]

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=4FE4B2AB.2030603@intel.com \
    --to=saul.wold@intel.com \
    --cc=liang.li@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.