From owner-freebsd-current@freebsd.org Fri Mar 17 17:31:23 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 BAE0FD10A8D for ; Fri, 17 Mar 2017 17:31:23 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 332461ADC for ; Fri, 17 Mar 2017 17:31:22 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([85.179.168.50]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LxLcc-1c9tqn3zXW-0170O9; Fri, 17 Mar 2017 18:31:20 +0100 Date: Fri, 17 Mar 2017 18:31:11 +0100 From: "O. Hartmann" To: Slawa Olhovchenkov Cc: "O. Hartmann" , freebsd-current Subject: Re: CURRENT: FreeBSD not reporting AES-NI on Intel(R) Xeon(R) CPU E5-1650 v3 Message-ID: <20170317183111.3a80f358@thor.intern.walstatt.dynvpn.de> In-Reply-To: <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> <20170317170735.GO70430@zxy.spb.ru> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/mE3R_Z4p_+.7jfIsOz8p6j4"; protocol="application/pgp-signature" X-Provags-ID: V03:K0:NsK/nTP2fqfBOJoR0JuVNfCh145bR0bGzUk6Jqo6NTV1647Esp4 +08+e2DmyU8tyEGBKTJk39QU0gznytLVK9/T4UDCsBcgpGwiq0H/cJTcHZ3T+Xu5cr17och 1FCJGlrndrtlUT0dx6OHMdKjker+PxsXlgjqvan0eqwBHE98gYXLkDL6/mqBj4Fnoak3BwP fpTkXFdJdQQAHQc2oPs7g== X-UI-Out-Filterresults: notjunk:1;V01:K0:WhBrNSeXGDs=:o7B5sy+YpDyxe/Bpr86XXW IkNZVw20jcI4tVLguq5kH/saj1hBUk+PuoekmsDwwgAFTUbCdGKh3LNDq6EBArxSn+Q41/7sp xqtisUtfxScdA/XnmaxOmzitbPPOQ/hm48VCu+hBwTYALXfMa2LUxV5Fi8FV5iHVHKPs8BQ57 8s+NqtrGPQdK9YX4ZTK/xMJawOhDxrGSfWDdka8P+hzbngzPaHJaWbE563h8DnI22nuJrJma1 da9/SaLxqLQJRQ0SXeq4cYA9n+b7+p3zyd2eJY3oNq8nmhPv2lLoMWzHbP8jKwRBd2XggK8Mm vPgyNPHxEP4mo8EG3piuLgilGVWNKPiMM/Ej0oJKz+ugRm5pAfLsJsy0HlxzhhxAVD2yCWlkV IVPpQTAibvjlkZrMT1W3xN31wTwLd6Kplnaw0hJaQMhf9U7WdGFWqx3jBKrVGa34fyCMMeie+ F4RtplPyVQRZl3y+dEuC54qR2f+yRnsoojS9iY0f4iyXmV5drMZaecP3WZrLnfdMD8huv2ihW EG4RL0R4BvQKREhmzpMabiaxgAB8AUG1a18xdKx67Xh8tvkArsh4CG5RjFViQ0Omoe+BtLbF8 QRXaMbylZnMG1EQveP54DO6gOGBsiU7yFem9UHLHVC3eVqNFbzj0zWOM2cl8vtUxXsmQ2WZaU /dfcAMoUJEFVgn1iy1nRXCzwxiRplmcvjLoyXcrUz+hR/UfTkoZ+y683b2b4zgRoWJdzoRSUv t3lUrQVr7Oeyd/245GLwzgqGWBRfyaH5Ai2NQtIH2lRwqHCyPcXUcgH8gnw= 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: Fri, 17 Mar 2017 17:31:23 -0000 --Sig_/mE3R_Z4p_+.7jfIsOz8p6j4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am Fri, 17 Mar 2017 20:07:35 +0300 Slawa Olhovchenkov schrieb: > On Fri, Mar 17, 2017 at 05:53:24PM +0100, O. Hartmann wrote: >=20 > > Am Fri, 17 Mar 2017 15:04:29 +0300 > > Slawa Olhovchenkov schrieb: > > =20 > > > On Fri, Mar 17, 2017 at 12:36:25PM +0100, O. Hartmann wrote: > > > =20 > > > > Running recent CURRENT on a Fujitsu Celsius M740 equipted with an I= ntel(R) > > > > Xeon(R) CPU E5-1650 v3 @ 3.50GHz CPU makes me some trouble. > > > >=20 > > > > FreeBSD does not report the existence or availability of AES-NI fea= ture, which > > > > is supposed to be a feature of this type of CPU: =20 > > >=20 > > > What reassons to detect AES-NI by FreeBSD? =20 > >=20 > > 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 c= ircumstances > > why FBSD won't. I do not know, that is the reason why I'm asking here. = =20 >=20 > This sample can have disabled AES-NI by vendor, in BIOS, for example. > As I show by links this is posible. >=20 > CPUID in you example don't show AES-NI capabilities, for example > 1650v4 w/ AES-NI >=20 > CPU: Intel(R) Xeon(R) CPU E5-1650 v4 @ 3.60GHz (3600.07-MHz K8-class CPU) > Origin=3D"GenuineIntel" Id=3D0x406f1 Family=3D0x6 Model=3D0x4f Step= ping=3D1 > Features=3D0xbfebfbff > Features2=3D0x7ffefbff > = = ^^^^^^ > AMD Features=3D0x2c100800 > AMD Features2=3D0x121 > Structured Extended > Features=3D0x21cbfbb > XSAVE Features=3D0x1 VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,Po= stIntr > TSC: P-state invariant, performance statistics >=20 > In you sample: "TSCDLT,XSAVE" >=20 > May be AES-NI disabled by vendor and FreeBSD correct show this. Or some b= ug in FreeBSD, > AES-NI work and other OS show AES-NI capabilities. >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" We have some LGA1151 XEON based 19 inch rack server, also equipted with Has= well E3-12XX-v3 XEONs and FreeBSD, also CURRENT, does show AES-NI. You're right, the vendor could have disabled AES-NI by intention - but they= offered this box especially with AES-NI capabilities.=20 See here: http://freebsd.1045724.x6.nabble.com/r285947-broken-AESNI-support-No-aesn= i0-on-Intel-XEON-E5-1650-v3-on-Fujitsu-Celsius-M740-td6028895.html I feel a bit pissed off right now due to Fujitsu, because we started testin= g some encrypting features and I'd like to use AES-NI and I run into this issue ag= ain. I need to know that FreeBSD is not the issue with this specific CPU type. I= 'm still frustrated by that stupid comment "UNIX is not supoorted" I got that time t= hen when I reported 2015 the issue to Fujitsu. --=20 O. Hartmann Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Abs.= 4 BDSG). --Sig_/mE3R_Z4p_+.7jfIsOz8p6j4 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWMwdXwAKCRDS528fyFhY lPbeAf4s2Q/Pr9/YJqUTUpdZtqiOo6Ch10ZkQeCSEaVjIi+zzkxkMgg5Kqooj8YD G+JFqLX4jhsojeWoLg/09EfWUbIfAf9sAQc+PylLTB/nhFwtUpuKSt3ViTO9MPee PHcUxPN2RF0I82LyQV9cUcPE9kvnCTj/aYnnfC4Tuui7x3juqi/1 =oxwG -----END PGP SIGNATURE----- --Sig_/mE3R_Z4p_+.7jfIsOz8p6j4--