On 19 Mar 2017, at 13:36, Rozhuk Ivan <rozhuk...@gmail.com> wrote: > > On Fri, 17 Mar 2017 17:53:24 +0100 > "O. Hartmann" <ohartm...@walstatt.org> wrote: > >>> Other OS detect AES-NI on this server? >> >> I havn't ried so far, the box is in heavy use. I'd like to check with >> some live USB drive versions and report later. >> > > You can write or find some program that read and decode CPUID and check > AES-NI support without reboot.
The kernel already does this at boot time, and show the results, e.g.: CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (3391.68-MHz 686-class CPU) Origin="GenuineIntel" Id=0x306a9 Family=0x6 Model=0x3a Stepping=9 Features=0xfa3fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,DTS,MMX,FXSR,SSE,SSE2,SS> Features2=0xffba2203<SSE3,PCLMULQDQ,SSSE3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND,HV> AMD Features=0x28100000<NX,RDTSCP,LM> AMD Features2=0x1<LAHF> Structured Extended Features=0x202<TSCADJ,ERMS> TSC: P-state invariant Unfortunately the kernel does not expose this information via any sysctl, so some time after booting it may have "scrolled away" in dmesg. In that case, you can use either the misc/cpuid or the sysutils/cpuid ports to show this information, and even quite a lot more. -Dimitry
Description: Message signed with OpenPGP