From owner-freebsd-current@freebsd.org  Sun Mar 19 16:03:11 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 5BFCED13153
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 19 Mar 2017 16:03:11 +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 1DBA0B95;
 Sun, 19 Mar 2017 16:03:11 +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 1cpdIS-000E9H-LZ; Sun, 19 Mar 2017 19:03:08 +0300
Date: Sun, 19 Mar 2017 19:03:08 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Dimitry Andric <dim@FreeBSD.org>
Cc: Rozhuk Ivan <rozhuk.im@gmail.com>, "O. Hartmann" <ohartmann@walstatt.org>,
 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: <20170319160308.GV70430@zxy.spb.ru>
References: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de>
 <20170317120429.GX15630@zxy.spb.ru>
 <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de>
 <20170319153658.7f2b0038@rimwks>
 <AD58DDA1-235A-4328-BCA6-E3A71DFA9A51@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AD58DDA1-235A-4328-BCA6-E3A71DFA9A51@FreeBSD.org>
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: Sun, 19 Mar 2017 16:03:11 -0000

On Sun, Mar 19, 2017 at 04:58:40PM +0100, Dimitry Andric wrote:

> On 19 Mar 2017, at 13:36, Rozhuk Ivan <rozhuk.im@gmail.com> wrote:
> > 
> > On Fri, 17 Mar 2017 17:53:24 +0100
> > "O. Hartmann" <ohartmann@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.

/var/run/dmesg.boot