From: cdall@cs.columbia.edu (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: fix pmd flushing in map_init_section
Date: Fri, 14 Jun 2013 09:54:17 -0700 [thread overview]
Message-ID: <20130614165417.GP3245@lvm> (raw)
In-Reply-To: <20130614164831.GA3387@e106331-lin.cambridge.arm.com>
On Fri, Jun 14, 2013 at 05:48:31PM +0100, Mark Rutland wrote:
> On Fri, Jun 14, 2013 at 05:34:09PM +0100, Christoffer Dall wrote:
> > On Fri, Jun 14, 2013 at 05:22:22PM +0100, Mark Rutland wrote:
> > > In e651eab0af: "ARM: 7677/1: LPAE: Fix mapping in alloc_init_section for
> > > unaligned addresses", the pmd flushing was broken when split out to
> > > map_init_section. At the end of the final iteration of the while loop,
> > > pmd will point at the pmd_t immediately after the pmds we updated, and
> > > thus flush_pmd_entry(pmd) won't flush the newly modified pmds. This has
> > > been observed to prevent an 11MPCore system from booting.
> > >
> > > This patch fixes this by remembering the address of the first pmd we
> > > update and using this as the argument to flush_pmd_entry.
> > >
> > > Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> > > Cc: R Sricharan <r.sricharan@ti.com>
> > > Cc: Catalin Marinas <catalin.marinas@arm.com>
> > > Cc: Christoffer Dall <cdall@cs.columbia.edu>
> > > Cc: Russell King <rmk+kernel@arm.linux.org.uk>
> > > Cc: stable at vger.kernel.org
> > > ---
> > > arch/arm/mm/mmu.c | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c
> > > index e0d8565..22bc0ff 100644
> > > --- a/arch/arm/mm/mmu.c
> > > +++ b/arch/arm/mm/mmu.c
> > > @@ -620,6 +620,7 @@ static void __init map_init_section(pmd_t *pmd, unsigned long addr,
> > > unsigned long end, phys_addr_t phys,
> > > const struct mem_type *type)
> > > {
> > > + pmd_t *p = pmd;
> > > #ifndef CONFIG_ARM_LPAE
> > > /*
> > > * In classic MMU format, puds and pmds are folded in to
> > > @@ -638,7 +639,7 @@ static void __init map_init_section(pmd_t *pmd, unsigned long addr,
> > > phys += SECTION_SIZE;
> > > } while (pmd++, addr += SECTION_SIZE, addr != end);
> > >
> > > - flush_pmd_entry(pmd);
> > > + flush_pmd_entry(p);
> > > }
> > >
> > > static void __init alloc_init_pmd(pud_t *pud, unsigned long addr,
> > > --
> >
> > Refresh my memory here again, why are we not flushing every pmd entry we
> > update? Is it because we assume the cache lines cover the maximum span
> > between addr and end?
>
> Yup, we assume a minimum cache line size of 8 bytes. I'm not so keen on this,
> but I suspect others might not be happy with moving the flush into the loop.
>
A comment on the call to flush_pmd_entry could solve it.
> >
> > Theoretically, shouldn't you also increment p in the non-LPAE case?
>
> Yes, I should. v2 shortly...
>
> Thanks,
> Mark.
next prev parent reply other threads:[~2013-06-14 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 16:22 [PATCH] arm: fix pmd flushing in map_init_section Mark Rutland
2013-06-14 16:34 ` Christoffer Dall
2013-06-14 16:48 ` Mark Rutland
2013-06-14 16:54 ` Christoffer Dall [this message]
2013-06-14 16:57 ` [PATCHv2] " Mark Rutland
2013-06-14 17:04 ` Christoffer Dall
2013-06-14 17:29 ` Catalin Marinas
2013-06-14 17:28 ` [PATCH] " Catalin Marinas
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=20130614165417.GP3245@lvm \
--to=cdall@cs.columbia.edu \
--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 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).