From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:47612)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1TKaED-0006p9-0c
	for qemu-devel@nongnu.org; Sat, 06 Oct 2012 15:40:01 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1TKaEC-0003lB-2B
	for qemu-devel@nongnu.org; Sat, 06 Oct 2012 15:40:00 -0400
Received: from gate.crashing.org ([63.228.1.57]:59949)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <benh@kernel.crashing.org>) id 1TKaEB-0003l0-Pp
	for qemu-devel@nongnu.org; Sat, 06 Oct 2012 15:39:59 -0400
Message-ID: <1349552373.4260.107.camel@pasglop>
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Date: Sun, 07 Oct 2012 06:39:33 +1100
In-Reply-To: <20121006145449.GZ29302@truffula.fritz.box>
References: <CAF+Cadt0BoZtRByGVP2rFgSNaDNn6B=O4h3uON4HwUDSWR27bA@mail.gmail.com>
	<5050B005.9080500@suse.de> <1347486505.2276.13.camel@pasglop>
	<878vbl7zgd.fsf@codemonkey.ws> <1349470153.4260.74.camel@pasglop>
	<20121006145449.GZ29302@truffula.fritz.box>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
Subject: Re: [Qemu-devel] Enablig DLPAR capacity on QEMU pSeries
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Erlon Cruz <erlon.cruz@br.flextronics.com>, Alexander Graf <agraf@suse.de>, Anthony Liguori <anthony@codemonkey.ws>, qemu-devel@nongnu.org

On Sun, 2012-10-07 at 00:54 +1000, David Gibson wrote:
> I also don't see how it helps in this situation.  The hotplug will
> still be initiated by qemu, so we'd have to work out how qemu
> communicates the info to RTAS, and how RTAS communicates it to the
> kernel, doubling the work.

This is not about initiating the hotplug, this is about the resource
management. Those are two separate problems.

Cheers,
Ben.