From owner-freebsd-hackers@FreeBSD.ORG Mon Mar 5 17:44:55 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 496C6106566B for ; Mon, 5 Mar 2012 17:44:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 217578FC16 for ; Mon, 5 Mar 2012 17:44:55 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id CCF0A46B2D; Mon, 5 Mar 2012 12:44:54 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1DE18B940; Mon, 5 Mar 2012 12:44:54 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 5 Mar 2012 12:21:08 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203051221.08681.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 05 Mar 2012 12:44:54 -0500 (EST) Cc: Maninya M Subject: Re: CPUID and CPU STATE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2012 17:44:55 -0000 On Friday, March 02, 2012 2:20:00 am Maninya M wrote: > I was unable to get this information about the cpuid variable in the > scheduler source code. > How does cpuid get its value from the hardware? The cpuid is a software ID value assigned during boot. It is not directly related to any specific hardware IDs. > How is the CPUSTATES value obtained/changed with hardware in the source > code? Do you mean, does cp_time[] handle hardware changes (hotplug CPUs, etc.)? Currently that isn't supported, the kernel assumes the set of CPUs is static for a given boot's lifetime. -- John Baldwin