From owner-freebsd-current@FreeBSD.ORG Fri Jan 2 10:38:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01C4516A4CE for ; Fri, 2 Jan 2004 10:38:51 -0800 (PST) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8955443D55 for ; Fri, 2 Jan 2004 10:38:49 -0800 (PST) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (localhost [127.0.0.1]) i02IccZV011505; Fri, 2 Jan 2004 13:38:38 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)i02Icc1l011502; Fri, 2 Jan 2004 13:38:38 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Fri, 2 Jan 2004 13:38:37 -0500 (EST) From: Andre Guibert de Bruet To: Oliver Brandmueller In-Reply-To: <20040102095719.H665@light.sdf.com> Message-ID: <20040102131829.O9356@alpha.siliconlandmark.com> References: <20040102160847.GD38779@e-Gitt.NET> <20040102095719.H665@light.sdf.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: Hot Swapping CPUs? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 02 Jan 2004 18:38:51 -0000 On Fri, 2 Jan 2004, Tom wrote: > On Fri, 2 Jan 2004, Oliver Brandmueller wrote: > > > to the base functionality for CPU hot swapping. One would need (apart > > from a Motherboard that's able to that ;-)) some control over CPUs now, > > like disabling a physical CPU during runtime (which could also be done > > automatically on certain filure onditions). > > sysctl already exposes some variabled to control CPUs on an SMP system. > > It is a pretty hard to detect a CPU failure in software, because the > software detection will fail at the same time the CPU does. Right. A hardware watchdog is what's required to effectively check for fail{ed,ing} cpus. With software, you're left either polling or guessing that a cpu has gone offline for hardware reasons when it doesn't run anything on its queue. > > Is there any work in progress in this direction? Would be a very neat > > feature for high availability systems. Find me a x86 motherboard (with specs, preferably) that supports cpu failure-monitoring and hot-swapping and I'll volunteer time to hack up some code for you. (We have a need for this functionality in our x86-farm at work, so I'd get to do it on the clock. :) ) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/ >