From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Fix virtual kernel memory printing for sparsemem
Date: Tue, 4 May 2010 19:00:17 +0200 [thread overview]
Message-ID: <201005041900.17228.marek.vasut@gmail.com> (raw)
In-Reply-To: <1272990536.15948.13.camel@e102109-lin.cambridge.arm.com>
Dne ?t 4. kv?tna 2010 18:28:56 Catalin Marinas napsal(a):
> On Tue, 2010-05-04 at 17:18 +0100, Russell King - ARM Linux wrote:
> > On Tue, May 04, 2010 at 06:13:28PM +0200, Marek Vasut wrote:
> > > Dne ?t 25. b?ezna 2010 17:01:26 Catalin Marinas napsal(a):
> > > > On Thu, 2010-03-25 at 15:30 +0000, Russell King - ARM Linux wrote:
> > > > > On Thu, Mar 25, 2010 at 03:24:29PM +0000, Catalin Marinas wrote:
> > > > > > On Thu, 2010-03-25 at 15:10 +0000, Russell King - ARM Linux wrote:
> > > > > > > While this looks fine, I'd like to see a lot of Tested-by's
> > > > > > > against this before it's merged - we've had similar code in
> > > > > > > show_mem() which has proven to be quite problematical to get
> > > > > > > right for all the various different combinations we have.
> > > > > > >
> > > > > > > However, we also have the same method in show_mem() which we
> > > > > > > know works fine, so I'd also like to see the problem with
> > > > > > > using it in mem_init() fully analysed - rather than a
> > > > > > > "possibly because".
> > > > > >
> > > > > > I can remove the "possibly" part :). The page_count() is given a
> > > > > > page with some random flags and it thinks it's a compound page.
> > > > > > It than tries to access page->first which isn't set, hence the
> > > > > > error.
> > > > > >
> > > > > > The original code assumes that for a given node the map is
> > > > > > contiguous and it calculates the page as (map + pfn). This is
> > > > > > only true for flatmem. With sparsemem the page calculation is a
> > > > > > bit more complicated but handled by pfn_to_page().
> > > > >
> > > > > And show_mem() ? It seems to suffer from the same problem.
> > > >
> > > > And that's a patch which fixes both (but as you said, it would be
> > > > good if more people test it on various platforms).
> > > >
> > > >
> > > > ARM: Fix kernel memory printing for sparsemem
> > > >
> > > > From: Catalin Marinas <catalin.marinas@arm.com>
> > > >
> > > > The show_mem() and mem_init() function are assuming that the page map
> > > > is contiguous and calculates the start and end page of a bank using
> > > > (map + pfn). This fails with SPARSEMEM where pfn_to_page() must be
> > > > used.
> > > >
> > > > Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> > > > Cc: Will Deacon <Will.Deacon@arm.com>
> > > > Cc: Andreas Fenkart <andreas.fenkart@streamunlimited.com>
> > >
> > > Works perfectly on my machine. I have a PXA270 based device where I
> > > have to use sparsemem. Thanks, you can add my:
> > >
> > > Tested-by: Marek Vasut <marek.vasut@gmail.com>
> > >
> > > Russell, the patch looks fine, please apply, the stuff is really
> > > broken.
> >
> > It's great to see patches getting tested by others ;)
> >
> > Catalin - mind submitting this with Marek's tested-by please?
>
> Done (patch 6093/1).
Thanks for the fast response. Catalin, thanks for the patch.
Cheers
next prev parent reply other threads:[~2010-05-04 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 14:53 [PATCH] ARM: Fix virtual kernel memory printing for sparsemem Catalin Marinas
2010-03-25 15:10 ` Russell King - ARM Linux
2010-03-25 15:24 ` Catalin Marinas
2010-03-25 15:30 ` Russell King - ARM Linux
2010-03-25 15:37 ` Will Deacon
2010-03-25 16:01 ` Catalin Marinas
2010-03-25 17:46 ` Will Deacon
2010-05-04 16:13 ` Marek Vasut
2010-05-04 16:18 ` Russell King - ARM Linux
2010-05-04 16:28 ` Catalin Marinas
2010-05-04 17:00 ` Marek Vasut [this message]
2010-05-04 16:02 ` Marek Vasut
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=201005041900.17228.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.