And how does a "-metal" (ie: Bare metal) Google Compute Engine behave with this patch?

For data, here is pmc while iperf3 limited to 1Gb/s in place of the expected 2.5Gb/s:

Detected on:

rge0@pci0:2:0:0:        class=0x020000 rev=0x05 hdr=0x00 vendor=0x10ec device=0x8125 subvendor=0x10ec subdevice=0
x0123
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8125 2.5GbE Controller'                                                                         class      = network
    subclass   = ethernet

Need to manually load the module (not auto-loaded when detected).

In D53413#1219714, @cperciva wrote:

Does this work with cross-builds? I suspect that WSTAGEDIR is getting set to "" and then you're setting PKG_ABI based on /usr/bin/uname in the host system.

Why are we using PKG_ABI with NOPKGBASE?

(adding context)

we are using this patch since months now, and it works great (because it solve the problem mentionned)