[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20140114171644.d7b97b0501708afbeae7c841@linux-foundation.org>
Date: Tue, 14 Jan 2014 17:16:44 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Rientjes <rientjes@...gle.com>
Cc: Nathan Zimmer <nzimmer@....com>,
Tang Chen <tangchen@...fujitsu.com>,
Wen Congyang <wency@...fujitsu.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Yasuaki Ishimatsu <isimatu.yasuaki@...fujitsu.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Hedi <hedi@....com>, Mike Travis <travis@....com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC] hotplug, memory: move register_memory_resource out of the
lock_memory_hotplug
On Tue, 14 Jan 2014 17:05:42 -0800 (PST) David Rientjes <rientjes@...gle.com> wrote:
> On Tue, 14 Jan 2014, Andrew Morton wrote:
>
> > From: Andrew Morton <akpm@...ux-foundation.org>
> > Subject: mm/memory_hotplug.c: register_memory_resource() fixes
> >
> > - register_memory_resource() should not go BUG on ENOMEM. That's
> > appropriate at system boot time, but not at memory-hotplug time. Fix.
> >
> > - register_memory_resource()'s caller is incorrectly replacing
> > request_resource()'s -EBUSY with -EEXIST. Fix this by propagating
> > errors appropriately.
> >
>
> Unfortunately, -EEXIST is a special case return value for both
> acpi_memory_enable_device() and hv_mem_hot_add(), so they would need to be
> modified to agree concurrently with this change.
blah, OK, thanks, I'll drop it.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists