From owner-freebsd-current@freebsd.org Sun Mar 19 16:07:43 2017 Return-Path: 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 7C491D133C9 for ; Sun, 19 Mar 2017 16:07:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 EE218F3C; Sun, 19 Mar 2017 16:07:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id v2JG7XYi046018 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 19 Mar 2017 18:07:33 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua v2JG7XYi046018 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id v2JG7XH8046017; Sun, 19 Mar 2017 18:07:33 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 19 Mar 2017 18:07:33 +0200 From: Konstantin Belousov To: Dimitry Andric Cc: Rozhuk Ivan , "O. Hartmann" , Slawa Olhovchenkov , freebsd-current Subject: Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3 Message-ID: <20170319160733.GA43712@kib.kiev.ua> References: <20170317123625.60f1a508@freyja.zeit4.iv.bundesimmobilien.de> <20170317120429.GX15630@zxy.spb.ru> <20170317175324.27f1d59d@thor.intern.walstatt.dynvpn.de> <20170319153658.7f2b0038@rimwks> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Mar 2017 16:07:43 -0000 On Sun, Mar 19, 2017 at 04:58:40PM +0100, Dimitry Andric wrote: > On 19 Mar 2017, at 13:36, Rozhuk Ivan wrote: > > > > On Fri, 17 Mar 2017 17:53:24 +0100 > > "O. Hartmann" 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 > Features2=0xffba2203 > AMD Features=0x28100000 > AMD Features2=0x1 > Structured Extended Features=0x202 > 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. It is quite pointless to expose the information through a sysctl, because it is non-privileged and is available to usermode via execution of the CPUID instruction, which is utilized by utilities listed below. Also, look at cpucontrol -i. > > 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. Or better, sysutils/x86info.