From: Andrew Morton <akpm@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Nathan Zimmer <nzimmer@sgi.com>,
Tang Chen <tangchen@cn.fujitsu.com>,
Wen Congyang <wency@cn.fujitsu.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Hedi <hedi@sgi.com>, Mike Travis <travis@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] hotplug, memory: move register_memory_resource out of the lock_memory_hotplug
Date: Tue, 14 Jan 2014 17:16:44 -0800 [thread overview]
Message-ID: <20140114171644.d7b97b0501708afbeae7c841@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1401141702450.3375@chino.kir.corp.google.com>
On Tue, 14 Jan 2014 17:05:42 -0800 (PST) David Rientjes <rientjes@google.com> wrote:
> On Tue, 14 Jan 2014, Andrew Morton wrote:
>
> > From: Andrew Morton <akpm@linux-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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-01-15 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 18:24 Nathan Zimmer
2014-01-14 23:13 ` Andrew Morton
2014-01-15 1:05 ` David Rientjes
2014-01-15 1:16 ` Andrew Morton [this message]
2014-01-15 0:58 ` David Rientjes
2014-01-15 1:12 ` Yasuaki Ishimatsu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140114171644.d7b97b0501708afbeae7c841@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hedi@sgi.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nzimmer@sgi.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rientjes@google.com \
--cc=tangchen@cn.fujitsu.com \
--cc=travis@sgi.com \
--cc=wency@cn.fujitsu.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox