Date: Tue, 22 Dec 2020 16:22:27 +0000 From: bugzilla-noreply@freebsd.org To: geom@FreeBSD.org Subject: [Bug 242747] geli: AMD Epyc+GELI not using Hardware AES Message-ID: <bug-242747-14739-UVdJyUjixZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-242747-14739@https.bugs.freebsd.org/bugzilla/> References: <bug-242747-14739@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242747 --- Comment #25 from Conrad Meyer <cem@freebsd.org> --- Thanks, Eirik. Let me see if I can come up with some copy-paste incantatio= ns to try. I'm not a dtrace expert myself. :-) Load dtrace support: sudo kldload dtraceall First, to see if aesni functions are being hit at all: sudo dtrace -n 'fbt:aesni::entry { @[probefunc] =3D count() }' Let it run for maybe a few seconds while there is any mild load to the GELI disks, then hit Ctrl-C. After Ctrl-C, wait a few seconds for dtrace to pri= nt output and exit. If the output is empty, nothing is calling into aesni.=20 Otherwise, you should see a listing of (aesni) function name, invocation co= unt pairs. If you get anything from the earlier trace, the following one should print = out (approximately) any errors returned by aesni functions (columns are: functi= on, error number, count): sudo dtrace -n 'fbt:aesni::return /arg1 > 0 && arg1 < 1000/ { @[probefunc,arg1] =3D count() }' --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242747-14739-UVdJyUjixZ>