From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755227Ab2LLX5F (ORCPT ); Wed, 12 Dec 2012 18:57:05 -0500 Received: from mail-pb0-f46.google.com ([209.85.160.46]:62828 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754815Ab2LLX5C (ORCPT ); Wed, 12 Dec 2012 18:57:02 -0500 Date: Wed, 12 Dec 2012 15:56:57 -0800 From: Greg KH To: Toshi Kani Cc: rjw@sisk.pl, lenb@kernel.org, akpm@linux-foundation.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, bhelgaas@google.com, isimatu.yasuaki@jp.fujitsu.com, jiang.liu@huawei.com, wency@cn.fujitsu.com, guohanjun@huawei.com, yinghai@kernel.org, srivatsa.bhat@linux.vnet.ibm.com Subject: Re: [RFC PATCH 00/11] Hot-plug and Online/Offline framework Message-ID: <20121212235657.GD22764@kroah.com> References: <1355354243-18657-1-git-send-email-toshi.kani@hp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1355354243-18657-1-git-send-email-toshi.kani@hp.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 12, 2012 at 04:17:12PM -0700, Toshi Kani wrote: > This patchset is an initial prototype of proposed hot-plug framework > for design review. The hot-plug framework is designed to provide > the common framework for hot-plugging and online/offline operations > of system devices, such as CPU, Memory and Node. While this patchset > only supports ACPI-based hot-plug operations, the framework itself is > designed to be platform-neural and can support other FW architectures > as necessary. > > The patchset has not been fully tested yet, esp. for memory hot-plug. > Any help for testing will be very appreciated since my test setup > is limited. > > The patchset is based on the linux-next branch of linux-pm.git tree. > > Overview of the Framework > ========================= Why all the new framework, doesn't the existing bus infrastructure provide everything you need here? Shouldn't you just be putting your cpus and memory sticks on a bus and handle stuff that way? What makes these types of devices so unique from all other devices that Linux has been handling in a dynamic manner (i.e. hotplugging them) for many many years? Why are you reinventing the wheel? confused, greg k-h