From: Andrew Morton <akpm00@gmail.com>
To: Nathan Fontenot <nfont@austin.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Greg KH <gregkh@suse.de>
Subject: Re: [PATCH] memory hotplug: Correct page reservation checking
Date: Mon, 3 Oct 2011 17:50:22 -0700 [thread overview]
Message-ID: <20111003175022.50cbef7f.akpm00@gmail.com> (raw)
In-Reply-To: <4E8098B9.1080702@austin.ibm.com>
On Mon, 26 Sep 2011 10:22:33 -0500
Nathan Fontenot <nfont@austin.ibm.com> wrote:
> The check to ensure that pages of recently added memory sections are correctly
> marked as reserved before trying to online the memory is broken. The request
> to online the memory fails with the following:
>
> kernel: section number XXX page number 256 not reserved, was it already online?
>
> This updates the page reservation checking to check the pages of each memory
> section of the memory block being onlined individually.
Why was this only noticed now? Is there something unusual about the
way in which you're using it, or has nobody ever used this code, or...?
next prev parent reply other threads:[~2011-10-04 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 15:22 [PATCH] memory hotplug: Correct page reservation checking Nathan Fontenot
2011-10-04 0:50 ` Andrew Morton [this message]
2011-10-04 14:19 ` Nathan Fontenot
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=20111003175022.50cbef7f.akpm00@gmail.com \
--to=akpm00@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nfont@austin.ibm.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