Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758111AbYC0BZs (ORCPT ); Wed, 26 Mar 2008 21:25:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754932AbYC0BZk (ORCPT ); Wed, 26 Mar 2008 21:25:40 -0400 Received: from relay2.sgi.com ([192.48.171.30]:34936 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754261AbYC0BZj (ORCPT ); Wed, 26 Mar 2008 21:25:39 -0400 Date: Wed, 26 Mar 2008 18:23:35 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Jeremy Fitzhardinge cc: Dave Hansen , KAMEZAWA Hiroyuki , Yasunori Goto , Linux Kernel Mailing List , Anthony Liguori , Chris Wright Subject: Re: Trying to make use of hotplug memory for xen balloon driver In-Reply-To: <1206576544.7883.21.camel@nimitz.home.sr71.net> Message-ID: References: <47EAD83A.2000000@goop.org> <1206576544.7883.21.camel@nimitz.home.sr71.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 774 Lines: 19 On Wed, 26 Mar 2008, Dave Hansen wrote: > You might also note that most of the ppc64 memory hotplug is driven by > userspace. The hypervisor actually contacts a daemon on the guest to > tell it where its new memory is. That daemon does the addition > through /sys/devices/system/memory/probe. Would it be possible to have the balloon driver use the memory hotplug interface instead? That would generalize the memory hotplug logic and you will likely find that lots of issues have already been addressed in that code. -- 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/