[dpdk-dev] [PATCH v9 00/14] Arm build options rework

[Dharmik Thakkar]

> On Nov 11, 2020, at 7:18 AM, Juraj Linkeš <juraj.linkes at pantheon.tech> wrote:
> 
> The current way of specifying Arm configuration options is insufficient
> since we can't identify the SoC we're building for from the MIDR
> information. For example, we can't distinguish between N1SDP, Graviton2
> or Ampere Altra.
> 
> Add a way to specify the cpu count and numa node count for cross builds
> and aarch64 -> aarch64 (SoC) builds.
> 
> We also want to be able to disable which drivers (and possibly
> libraries) are built without user input. This is useful when building:
> 1. on an SoC that is slow and we want to build only what is necessary
>  without the user having to check which libraries they have installed
> 2. a cross build on a fast aarch64 machine but with target SoC which
>  differs in capabilities or libraries.
> This is achieved by specifying the drivers in SoC configuration.
> 
> Among libraries, only libnuma can be now disabled.
> 
> Also add an optional way to discover cpu count a numa node count. Fix
> -Dmax_lcores and -Dmax_numa_nodes for arm builds.
> 
> The current implementation adds/supports the following:
> * x86 -> aarch64 cross build with added config options/disabled
>  drivers/libs
> * aarch64 -> aarch64 builds for a different SoCs using meson -Darm_soc
>  option or using a cross file
> * max numa nodes and max lcore may be specified on the command line to
>  overwrite the values for any (native, SoC or cross) build
> 

Tested ok on N1SDP and ThunderX2. No regression seen with testpmd and l3fwd.
Tested using native build, default build and using arm_soc option.
Series Tested-by: Dharmik Thakkar <dharmik.thakkar at arm.com>