From owner-freebsd-current@freebsd.org  Wed Jan  3 06:05:25 2018
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 D6639EAEB62
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed,  3 Jan 2018 06:05:25 +0000 (UTC)
 (envelope-from cy.schubert@komquats.com)
Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "Client", Issuer "CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id ABDE865B74
 for <freebsd-current@freebsd.org>; Wed,  3 Jan 2018 06:05:25 +0000 (UTC)
 (envelope-from cy.schubert@komquats.com)
Received: from spqr.komquats.com ([96.50.22.10]) by shaw.ca with ESMTPA
 id WcAueIRfCb3YIWcAweZf4y; Tue, 02 Jan 2018 23:05:19 -0700
X-Authority-Analysis: v=2.2 cv=J/va1EvS c=1 sm=1 tr=0
 a=jvE2nwUzI0ECrNeyr98KWA==:117 a=jvE2nwUzI0ECrNeyr98KWA==:17
 a=RgaUWeydRksA:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=adqX0pXGAAAA:8
 a=VoFzOySMKdiBq0rub64A:9 a=b5NKUVClZKskcM8I:21 a=sjQDjPxzyfQ2nWA5:21
 a=CjuIK1q_8ugA:10 a=fAouFcOKkmgthFq3ck8A:9 a=5YBYamX1noHTuYor:21
 a=Ff0qx1Xp12TPAcau:21 a=e1fQtxgZ-4rG_Hz7:21 a=_W_S_7VecoQA:10
 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 a=0l7XRIR7vdP6TgInZwrD:22
Received: from [25.172.217.252] (unknown [24.114.27.5])
 by spqr.komquats.com (Postfix) with ESMTPSA id D522D1C7;
 Tue,  2 Jan 2018 22:05:15 -0800 (PST)
MIME-Version: 1.0
From: Cy Schubert <Cy.Schubert@komquats.com>
Subject: RE: Intel CPU design flaw - FreeBSD affected?
Date: Tue, 2 Jan 2018 22:05:27 -0800
To: Kurt Jaeger <lists@opsec.eu>
CC: FreeBSD Current <freebsd-current@freebsd.org>
Message-Id: <20180103060515.D522D1C7@spqr.komquats.com>
X-CMAE-Envelope: MS4wfEApJHjwGyzEtomnUf31SRvSgQnDN8rNg6p109SUuhQxpyezg+/N3k+E5v5ltIPkcp6lqcLO6zm1voelSMYyd5uGzd8VRA13uu1T57Sr0ovSpVAVykfU
 DuPFEIVz01wMhYejMx/sezBzAUtOBgUI5V+oZ3BH0L0M4MaRKk6zdNIegu4b1hK8d/p2+TbrwQ+Qfw==
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.25
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
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: Wed, 03 Jan 2018 06:05:25 -0000

Sorry, cpuid.

---
Sent using a tiny phone keyboard.
Apologies for any typos and autocorrect.
Also, this old phone only supports top post. Apologies.

Cy Schubert
<Cy.Schubert@cschubert.com> or <cy@freebsd.org>
The need of the many outweighs the greed of the few.
---

-----Original Message-----
From: Kurt Jaeger
Sent: 02/01/2018 21:41
To: Cy Schubert
Cc: FreeBSD Current
Subject: Re: Intel CPU design flaw - FreeBSD affected?

Hi!

> You can see if your cpu supports pcid using cpuinfo from ports.

portfind cpuinfo

finds sysutils/p5-Linux-Cpuinfo, but this does not provide a cpuinfo
command ?

--=20
pi@opsec.eu            +49 171 3101372                         2 years to g=
o !