From: Andrew Morton <akpm@linux-foundation.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-mm@kvack.org, gerald.schaefer@de.ibm.com, rjw@sisk.pl,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow memory hotplug and hibernation in the same kernel
Date: Fri, 13 Nov 2009 15:51:02 -0800 [thread overview]
Message-ID: <20091113155102.3480907f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20091113105944.GA16028@basil.fritz.box>
On Fri, 13 Nov 2009 11:59:44 +0100
Andi Kleen <andi@firstfloor.org> wrote:
> Allow memory hotplug and hibernation in the same kernel
>
> Memory hotplug and hibernation was excluded in Kconfig. This is obviously
> a problem for distribution kernels who want to support both in the same
> image.
>
> After some discussions with Rafael and others the only problem is
> with parallel memory hotadd or removal while a hibernation operation
> is in process. It was also working for s390 before.
>
> This patch removes the Kconfig level exclusion, and simply
> makes the memory add / remove functions grab the pm_mutex
> to exclude against hibernation.
>
> ...
>
> +extern struct mutex pm_mutex;
Am a bit worried by the new mutex.
> #ifndef CONFIG_HIBERNATION
> static inline void register_nosave_region(unsigned long b, unsigned long e)
> {
> @@ -308,8 +310,23 @@ static inline void register_nosave_regio
> static inline void register_nosave_region_late(unsigned long b, unsigned long e)
> {
> }
> -#endif
>
> -extern struct mutex pm_mutex;
> +static inline void lock_hibernation(void) {}
> +static inline void unlock_hibernation(void) {}
> +
> +#else
> +
> +/* Let some subsystems like memory hotadd exclude hibernation */
> +
> +static inline void lock_hibernation(void)
> +{
> + mutex_lock(&pm_mutex);
> +}
> +
> +static inline void unlock_hibernation(void)
> +{
> + mutex_unlock(&pm_mutex);
> +}
> +#endif
Has this been carefully reviewed and lockdep-tested to ensure that we
didn't introduce any ab/ba nasties?
--
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:[~2009-11-13 23:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 10:59 Andi Kleen
2009-11-13 11:13 ` KOSAKI Motohiro
2009-11-13 11:32 ` KOSAKI Motohiro
2009-11-13 11:36 ` Andi Kleen
2009-11-13 11:35 ` Andi Kleen
2009-11-13 20:16 ` Rafael J. Wysocki
2009-11-14 0:15 ` Andi Kleen
2009-11-14 18:57 ` Rafael J. Wysocki
2009-11-13 23:51 ` Andrew Morton [this message]
2009-11-14 0:08 ` Andi Kleen
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=20091113155102.3480907f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=gerald.schaefer@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rjw@sisk.pl \
/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