On Fri, Mar 17, 2017 at 05:53:24PM +0100, O. Hartmann wrote:

> Am Fri, 17 Mar 2017 15:04:29 +0300
> Slawa Olhovchenkov <s...@zxy.spb.ru> schrieb:
> > On Fri, Mar 17, 2017 at 12:36:25PM +0100, O. Hartmann wrote:
> > 
> > > Running recent CURRENT on a Fujitsu Celsius M740 equipted with an Intel(R)
> > > Xeon(R) CPU E5-1650 v3 @ 3.50GHz CPU makes me some trouble.
> > > 
> > > FreeBSD does not report the existence or availability of AES-NI feature, 
> > > which
> > > is supposed to be a feature of this type of CPU:  
> > 
> > What reassons to detect AES-NI by FreeBSD?
> What do you mean? I do not understand! FreeBSD is supposed to read the CPUID 
> and
> therefore the capabilities as every other OS, too. But there may some 
> circumstances why
> FBSD won't. I do not know, that is the reason why I'm asking here.

This sample can have disabled AES-NI by vendor, in BIOS, for example.
As I show by links this is posible.

CPUID in you example don't show AES-NI capabilities, for example
1650v4 w/ AES-NI

CPU: Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz (3600.07-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x406f1  Family=0x6  Model=0x4f  Stepping=1
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended 
  XSAVE Features=0x1<XSAVEOPT>
  TSC: P-state invariant, performance statistics

In you sample: "TSCDLT,XSAVE"

May be AES-NI disabled by vendor and FreeBSD correct show this. Or some bug in 
FreeBSD, AES-NI work and other OS
show AES-NI capabilities.

freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to