On Tuesday 13 April 2010 21:16:44 Benjamin Herrenschmidt wrote:
> On Tue, 2010-04-13 at 16:02 +1000, Mark Nelson wrote:
> > 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_
On Tue, 2010-04-13 at 16:02 +1000, Mark Nelson wrote:
> 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 enab
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.
> >
> >
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 o
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 th
