From owner-freebsd-hackers@FreeBSD.ORG  Mon Aug  4 15:22:15 2014
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 8F2EDFEC
 for <freebsd-hackers@freebsd.org>; Mon,  4 Aug 2014 15:22:15 +0000 (UTC)
Received: from mail-ig0-x243.google.com (mail-ig0-x243.google.com
 [IPv6:2607:f8b0:4001:c05::243])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 642D12EE0
 for <freebsd-hackers@freebsd.org>; Mon,  4 Aug 2014 15:22:15 +0000 (UTC)
Received: by mail-ig0-f195.google.com with SMTP id uq10so1440021igb.2
 for <freebsd-hackers@freebsd.org>; Mon, 04 Aug 2014 08:22:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=TJsFEaxN5spuve3bjLXzpdVIsUUOWDwBLWC0GAVyq4I=;
 b=ukctVv2BV5okX+uWxwU77R0p086B1dKxn1cmuUJaQIoiKzHYA7Oe1Qantcv7DsLsKK
 IVzFRl5ZRdp50w9DlDtdPdsSZsjA7vTvabuQrQBDj32f+/IvOQPuX+OvljgvUtocoeXS
 zZrbLOubxdP6cZwiTK6mNXmiS1iFUA+9vphLhEef5FHENyx3olbr+YOKlKd+yo41Gab6
 sZRTUPq6sKkDhKVGZi9awGlhC6AcCeJs83slj5EM0YIa+TBclmg3cJkWpF/2u3IW7cwa
 CKr50sqtM/OUEkpFheNWjWdL0JuXHYE7a8xYrtqcuc4x1SpR4VAwigzKYSIhXgnooxdo
 DZnA==
MIME-Version: 1.0
X-Received: by 10.50.164.202 with SMTP id ys10mr37782734igb.6.1407165734684;
 Mon, 04 Aug 2014 08:22:14 -0700 (PDT)
Received: by 10.64.7.203 with HTTP; Mon, 4 Aug 2014 08:22:14 -0700 (PDT)
Date: Mon, 4 Aug 2014 08:22:14 -0700
Message-ID: <CAA3ZYrARe8mERCeLXnGT26QzMg=XncOaXkgzjp=eY9x1_U-Mag@mail.gmail.com>
Subject: Re: sysctl hw add nphyscpu variable
From: Dieter BSD <dieterbsd@gmail.com>
To: freebsd-hackers@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Aug 2014 15:22:15 -0000

> I think hw.nsocket would make more sense. Whoever does this should
> check to see if any other UNIX platforms have picked a suitable name.

There are other sockets besides cpu sockets, so it might be a good idea
to include something that says what kind of socket.  I was thinking
n_cpu_socket, which isn't perfect either, since there are other things
that can be plugged into cpu sockets.  FPGAs for one.  Is there a more
generic term for cpu socket?

>> Probable things will get complicated a bit if the system is a guest
>> under Xen or other hypervisor. But probable there the nphyscpu should
>> be NA ?
>
> The hypervisor is able to pass through a geometry, so this would still
> make sense there.

If you are running bochs on a non-x86 machine (Alpha, Sparc, ARM, ...),
you have a virtual cpu plugged into a virtual socket.