[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56938B7E.3060902@citrix.com>
Date: Mon, 11 Jan 2016 11:01:18 +0000
From: David Vrabel <david.vrabel@...rix.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>, <linux-mm@...ck.org>
CC: <linux-kernel@...r.kernel.org>, <linux-acpi@...r.kernel.org>,
"Jonathan Corbet" <corbet@....net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Daniel Kiper <daniel.kiper@...cle.com>,
Dan Williams <dan.j.williams@...el.com>,
Tang Chen <tangchen@...fujitsu.com>,
"David Rientjes" <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Xishi Qiu <qiuxishi@...wei.com>,
Mel Gorman <mgorman@...hsingularity.net>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Igor Mammedov <imammedo@...hat.com>,
Kay Sievers <kay@...y.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"Boris Ostrovsky" <boris.ostrovsky@...cle.com>
Subject: Re: [PATCH v3] memory-hotplug: add automatic onlining policy for
the newly added memory
On 07/01/16 17:23, Vitaly Kuznetsov wrote:
>
> - Changes since 'v1':
> Add 'online' parameter to add_memory_resource() as it is being used by
> xen ballon driver and it adds "empty" memory pages [David Vrabel].
> (I don't completely understand what prevents manual onlining in this
> case as we still have all newly added blocks in sysfs ... this is the
> discussion point.)
I'm not sure what you're not understanding here?
Memory added by the Xen balloon driver (whether populated with real
memory or not) does need to be onlined by udev or similar.
David
Powered by blists - more mailing lists