[dpdk-dev] [PATCH v16 1/3] build: disable/enable drivers in Arm builds

Bruce Richardson bruce.richardson at intel.com
Tue Mar 9 11:56:54 CET 2021


On Tue, Mar 09, 2021 at 08:58:39AM +0000, Juraj Linkeš wrote:
> Honnappa, Thomas, Bruce, Jerin, you've comments in the past. Do you have any further input?
> 
> I think we just need to agree on the allowlist/blocklist mechanism. The current commit allows specifying either an allowlist or a blocklist, but not both. However, it would possible to implement specifying both - first we'll allow what's in allowlist and then we'll remove from that set what's in blocklist. Thoughts?
> 

If we have both, I think limiting to only one is by far the sanest option.
I'm not fully convinced by the need to have both, since the blocklist
allows wildcarding and exception cases. For example "net/[!i]*" will
blocklist all net drivers except those starting with an "i". Admittedly,
for usability purposes having an allowlist might work better.

One final thought, if we add a driver allowlist for cross files, should we
also add one as a top-level meson option also for consistency?

/Bruce


More information about the dev mailing list