All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Cc: "saul.wold" <saul.wold@intel.com>
Subject: Re: [PATCH] linux-yocto-dev: Handle performance regression
Date: Fri, 8 Jul 2016 13:04:32 -0400	[thread overview]
Message-ID: <577FDD20.3000700@windriver.com> (raw)
In-Reply-To: <1467997249.28829.13.camel@linuxfoundation.org>

On 2016-07-08 01:00 PM, Richard Purdie wrote:
> After commit 0437a59e3c298d40aaa96af09b80bff8fcbe292d, the linux-yocto-dev
> recipe is being parsed every time we run "bitbake -p". This was spotted
> on some performance benchmarks and showed up as a performance regression.
>
> We can tweak the recipe to ensure this doesn't happen and that its only
> used if selected.

Makes sense to me.

Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>


>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> index 3085263..c50b319 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> @@ -20,6 +20,9 @@ include recipes-kernel/linux/linux-yocto-dev-revisions.inc
>   python () {
>       if d.getVar("PREFERRED_PROVIDER_virtual/kernel", True) != "linux-yocto-dev":
>           raise bb.parse.SkipPackage("Set PREFERRED_PROVIDER_virtual/kernel to linux-yocto-dev to enable it")
> +    else:
> +        d.setVar("SRCREV_machine", "${AUTOREV}")
> +        d.setVar("SRCREV_meta", "${AUTOREV}")
>   }
>
>   KBRANCH = "standard/base"
> @@ -33,8 +36,8 @@ SRC_URI = "git://git.yoctoproject.org/linux-yocto-dev.git;branch=${KBRANCH};name
>   # linux-yocto-dev is the preferred provider, they will be overridden to
>   # AUTOREV in following anonymous python routine and resolved when the
>   # variables are finalized.
> -SRCREV_machine ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
> -SRCREV_meta ?= '${@oe.utils.conditional("PREFERRED_PROVIDER_virtual/kernel", "linux-yocto-dev", "${AUTOREV}", "29594404d7fe73cd80eaa4ee8c43dcc53970c60e", d)}'
> +SRCREV_machine ?= "29594404d7fe73cd80eaa4ee8c43dcc53970c60e"
> +SRCREV_meta ?= "29594404d7fe73cd80eaa4ee8c43dcc53970c60e"
>
>   LINUX_VERSION ?= "4.6-rc+"
>   LINUX_VERSION_EXTENSION ?= "-yoctodev-${LINUX_KERNEL_TYPE}"
>
>



      reply	other threads:[~2016-07-08 17:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 17:00 [PATCH] linux-yocto-dev: Handle performance regression Richard Purdie
2016-07-08 17:04 ` Bruce Ashfield [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=577FDD20.3000700@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@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.