Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267516AbUIJP7j (ORCPT ); Fri, 10 Sep 2004 11:59:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267490AbUIJP4t (ORCPT ); Fri, 10 Sep 2004 11:56:49 -0400 Received: from shockwave.systems.pipex.net ([62.241.160.9]:21130 "EHLO shockwave.systems.pipex.net") by vger.kernel.org with ESMTP id S267507AbUIJPxI (ORCPT ); Fri, 10 Sep 2004 11:53:08 -0400 Date: Fri, 10 Sep 2004 16:53:40 +0100 (BST) From: Tigran Aivazian X-X-Sender: tigran@einstein.homenet To: Nathan Bryant Cc: Bill Davidsen , Subject: Re: Latest microcode data from Intel. In-Reply-To: <4141CCA8.30807@optonline.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 543 Lines: 15 On Fri, 10 Sep 2004, Nathan Bryant wrote: > Potentially stupid question, how does microcode update interact with CPU > hotplug? CPU hotplug? Is there such a thing as _working_ CPU hotplug support in Linux? (or any hardware that can actually allow unplugging/plugging CPUs?) Kind regards Tigran - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/