From: Mark Nelson <markn@au1.ibm.com>
To: michael@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc: Track backing pages allocated by vmemmap_populate()
Date: Tue, 13 Apr 2010 16:02:23 +1000 [thread overview]
Message-ID: <201004131602.23898.markn@au1.ibm.com> (raw)
In-Reply-To: <1271136257.13902.9.camel@concordia>
On Tuesday 13 April 2010 15:24:17 Michael Ellerman wrote:
> On Tue, 2010-04-13 at 14:16 +1000, Mark Nelson wrote:
> > We need to keep track of the backing pages that get allocated by
> > vmemmap_populate() so that when we use kdump, the dump-capture kernel knows
> > where these pages are.
> >
> > We use a linked list of structures that contain the physical address of the
> > backing page and corresponding virtual address to track the backing pages.
> > We can use an hlist to save space, because we never remove nodes.
>
> What if we remove_memory() ? Or does that not do what I think it does?
That's a good question, and one that I probably should have added to the
commit message.
But, following through, it looks like we end up calling into
__remove_section() from mm/memory_hotplug.c and if
CONFIG_SPARSEMEM_VMEMMAP is enabled we just return EBUSY as freeing
memmap with vmemmap isn't implemented yet.
So for the moment, I'm not sure we have to worry about it.
Thanks!
Mark.
next prev parent reply other threads:[~2010-04-13 5:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 7:12 [PATCH] powerpc: Track backing pages used allocated by vmemmap_populate() Mark Nelson
2010-04-13 4:16 ` [PATCH v2] powerpc: Track backing pages " Mark Nelson
2010-04-13 5:24 ` Michael Ellerman
2010-04-13 6:02 ` Mark Nelson [this message]
2010-04-13 11:16 ` Benjamin Herrenschmidt
2010-04-13 23:38 ` Mark Nelson
2010-04-22 2:21 ` [PATCH v3] " Mark Nelson
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=201004131602.23898.markn@au1.ibm.com \
--to=markn@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).