You can check if GCM cipher is available in the kernel (lsmod) or whatever the kernel might report to you.
I've just tried cipher-gcm on my Ubuntu 18.04 and I don't see any issues:

~/work/cryptodev-linux$ sudo insmod cryptodev.ko
~/work/cryptodev-linux$ ./tests/cipher-gcm
~/work/cryptodev-linux$ echo $?
0
~/work/cryptodev-linux$ dmesg |tail
...
[70607.810427] cryptodev: driver 1.11 loaded.
[70617.709616] cryptodev: cipher-gcm[8597] (adjust_sg_array:117): reallocating from 32 to 32 pages
[70617.709645] cryptodev: cipher-gcm[8597] (adjust_sg_array:117): reallocating from 32 to 32 pages
[70617.709671] cryptodev: cipher-gcm[8597] (adjust_sg_array:117): reallocating from 32 to 32 pages
[70617.709700] cryptodev: cipher-gcm[8597] (adjust_sg_array:117): reallocating from 32 to 32 pages

from cryptodev-linux.

Thanks, we leave CRYPTO_GCM not set.

CONFIG_CRYPTO_GCM is not set

we will try it again after GCM enabled.

we are using version of 1.8 --

dmesg |grep crypto

[ 1499.012327] cryptodev: driver 1.8 loaded.

thanks again.

from cryptodev-linux.

cipher-gcm run without any problem after recompiling kernel with GCM enabled.

from cryptodev-linux.