From owner-freebsd-hackers@freebsd.org Mon Feb 12 20:53:34 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1BFAF1BD02 for ; Mon, 12 Feb 2018 20:53:33 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from mr11p00im-asmtp001.me.com (mr11p00im-asmtp001.me.com [17.110.69.252]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 920DC6D3CC for ; Mon, 12 Feb 2018 20:53:33 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from process-dkim-sign-daemon.mr11p00im-asmtp001.me.com by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0P42009001121F00@mr11p00im-asmtp001.me.com> for freebsd-hackers@freebsd.org; Mon, 12 Feb 2018 20:52:58 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=04042017; t=1518468778; bh=fAPZ/sQXLnWNGeEMRPz93JNauMYjW6UjNdiRSGvCG9c=; h=Date:Subject:From:To:Message-id:MIME-version:Content-type; b=dmGMZWSdL6eoEQLDUGREegpYyAZFkO3R8K5B9bWFhs4bMOh+q5IuwlbjmhbMa9G1r c98t8ZyfTfcEb6c2v+exxt6dYbfrz8693ixa/cRV7jw93jpHavzkAJXzUNf3UZGSoi U/CPJW+Ky3EK39UAf7XnCQIgr1AXHXPT5QJStkNwRNRx0MceR6URpqjtGBTZvBXAZ1 PXTse3IyMjK1yrc+yE30sddlyu+Tvl9Fh7LMOghrZjLfOUb63Jz4vjxBrNeuL4bzZI YcS+Bkf3rghdVDS7OrCOWVmsGOurhrVhkLcxKywOqsN125S27Igt+3KRaWrZJ/p7Gg eaACGSJyV6fVQ== Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTPSA id <0P42009IV206LG00@mr11p00im-asmtp001.me.com> for freebsd-hackers@freebsd.org; Mon, 12 Feb 2018 20:52:58 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-02-12_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1802120265 User-Agent: Microsoft-MacOutlook/10.9.0.180116 Date: Mon, 12 Feb 2018 12:52:53 -0800 Subject: Request for information: quad- and/or octal-socket *bridge and/or *well systems From: Ravi Pokala To: "freebsd-hackers@freebsd.org" Message-id: <8B689420-111B-46B6-8A65-B3ECED3FAF79@mac.com> Thread-topic: Request for information: quad- and/or octal-socket *bridge and/or *well systems MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: quoted-printable X-Mailman-Approved-At: Mon, 12 Feb 2018 21:26:02 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 20:53:34 -0000 Hi folks, If you have access to a quad- or octal-socket =EF=BB=BF(Ivy|Sandy)bridge or (Has|= Broad)well system, could you run these commands and send me the output: pciconf -l | egrep ':(19|20|21|22|23|24):' egrep '^CPU| memory|FreeBSD/SMP' /var/run/dmesg.boot I'm working on a driver for a component of the integrated Memory Controller= , which is built into those CPUs, and I want to make sure I understand the w= ay things are enumerated on multi-socket systems. I'd even be satisfied with the Linux equivalents; the first gets the list o= f PCI devices whose device number is [19-24], along with their device-id inf= o; the second gets the CPU name, system memory, and socket / core / thread b= reakdown. Thanks, Ravi (rpokala@)