From owner-freebsd-current@freebsd.org  Fri Mar 17 17:07:39 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C010D1020C
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 17 Mar 2017 17:07:39 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1E4C41CD6
 for <freebsd-current@freebsd.org>; Fri, 17 Mar 2017 17:07:39 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1covLj-000MUr-AC; Fri, 17 Mar 2017 20:07:35 +0300
Date: Fri, 17 Mar 2017 20:07:35 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: "O. Hartmann" <ohartmann@walstatt.org>
Cc: freebsd-current <freebsd-current@freebsd.org>
Subject: Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU
 E5-1650 v3
Message-ID: <20170317170735.GO70430@zxy.spb.ru>
References: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de>
 <20170317120429.GX15630@zxy.spb.ru>
 <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Mar 2017 17:07:39 -0000

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

> Am Fri, 17 Mar 2017 15:04:29 +0300
> Slawa Olhovchenkov <slw@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
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x7ffefbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
                                                                                                                                                       ^^^^^^
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x121<LAHF,ABM,Prefetch>
  Structured Extended Features=0x21cbfbb<FSGSBASE,TSCADJ,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,PQM,NFPUSG,PQE,RDSEED,ADX,SMAP,PROCTRACE>
  XSAVE Features=0x1<XSAVEOPT>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  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.