All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: Denys Dmytriyenko <denys@konsulko.com>,
	Ryan Eatmon <reatmon@ti.com>,
	meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master/kirkstone][PATCH] conf: machine: k3: Use Cortex-A53/A72 CPU tune
Date: Fri, 16 Feb 2024 15:23:00 -0500	[thread overview]
Message-ID: <20240216202300.GC1572@denix.org> (raw)
In-Reply-To: <20240215212613.57012-1-afd@ti.com>

Unfortunately, NAK.

This is considered an antisocial behavior for a BSP in the Yocto Project 
world. And the performance benefit is questionable with 1%-2%, if at all.

The proper place for any extra optimization tunes is in a distro config. Maybe 
even by end customer's final product, not a reference distro.

Consider a distro that supports multiple HW platforms and uses multiple BSPs 
besides meta-ti - YoE, AGL, etc. You do want a common denominator tunes in 
order to get the most binary re-use across the platforms.

For example, AGL goes to some extreme lengths to override such custom tunes 
set by misbehaving BSPs and it's quite ugly.

And moreover, we've gone through this motion in the past many years ago when 
we had our ARMv7 platforms set to their corresponding cortex-a8/a9/a15 tunes 
by default, but eventually ended up setting a common ARMv7 tune:

DEFAULTTUNE ?= "armv7athf-neon"

So, you should either leave the current arch-arm64.inc inclusion as is, or if 
you insist on including tune-cortexa72-cortexa53.inc, set the default tune 
back to plain aarch64:

DEFAULTTUNE ?= "aarch64"


On Thu, Feb 15, 2024 at 03:26:13PM -0600, Andrew Davis via lists.yoctoproject.org wrote:
> All current K3 devices use either A53 or A72. Use the compile tune
> configuration specific for these to allow the compiler to make
> better optimizations.
> 
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
>  meta-ti-bsp/conf/machine/include/k3.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-ti-bsp/conf/machine/include/k3.inc b/meta-ti-bsp/conf/machine/include/k3.inc
> index 2415f0ba..7c3579af 100644
> --- a/meta-ti-bsp/conf/machine/include/k3.inc
> +++ b/meta-ti-bsp/conf/machine/include/k3.inc
> @@ -3,7 +3,7 @@
>  require conf/machine/include/ti-soc.inc
>  SOC_FAMILY:append = ":k3"
>  
> -require conf/machine/include/arm/arch-arm64.inc
> +require conf/machine/include/arm/armv8a/tune-cortexa72-cortexa53.inc
>  
>  BBMULTICONFIG += "k3r5"
>  
> -- 
> 2.39.2


  parent reply	other threads:[~2024-02-16 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15 21:26 [meta-ti][master/kirkstone][PATCH] conf: machine: k3: Use Cortex-A53/A72 CPU tune Andrew Davis
2024-02-16  7:07 ` [EXTERNAL] " Limaye, Aniket
2024-02-16 20:23 ` Denys Dmytriyenko [this message]
2024-02-20 14:31   ` Andrew Davis
2024-02-20 15:00     ` Ryan Eatmon

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=20240216202300.GC1572@denix.org \
    --to=denis@denix.org \
    --cc=afd@ti.com \
    --cc=denys@konsulko.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=reatmon@ti.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.