From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Hoeun Ryu <hoeun.ryu@gmail.com>
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm:lpae: build TTB control register value from scratch in v7_ttb_setup
Date: Sat, 10 Jun 2017 11:19:43 +0100 [thread overview]
Message-ID: <20170610101943.GW4902@n2100.armlinux.org.uk> (raw)
In-Reply-To: <448EF961-9178-4A3F-8995-F4E3466F4A92@gmail.com>
On Sat, Jun 10, 2017 at 01:43:24PM +0900, Hoeun Ryu wrote:
> Hello, Russell and Robin.
>
> Would you please review this patch ?
I think it's fine, thanks.
>
> Than you
>
> > On Jun 7, 2017, at 11:39 AM, Hoeun Ryu <hoeun.ryu@gmail.com> wrote:
> >
> > Reading TTBCR in early boot stage might return the value of the previous
> > kernel's configuration, especially in case of kexec. For example, if
> > normal kernel (first kernel) had run on a configuration of PHYS_OFFSET <=
> > PAGE_OFFSET and crash kernel (second kernel) is running on a configuration
> > PHYS_OFFSET > PAGE_OFFSET, which can happen because it depends on the
> > reserved area for crash kernel, reading TTBCR and using the value to OR
> > other bit fields might be risky because it doesn't have a reset value for
> > TTBCR.
> >
> > Suggested-by: Robin Murphy <robin.murphy@arm.com>
> > Signed-off-by: Hoeun Ryu <hoeun.ryu@gmail.com>
> > ---
> >
> > * v1: amended based on
> > - "[PATCHv2] arm: LPAE: kexec: clear TTBCR.T1SZ explicitly when
> > PHYS_OFFSET > PAGE_OFFSET"
> > - https://lkml.org/lkml/2017/6/5/239
> >
> > arch/arm/mm/proc-v7-3level.S | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/arch/arm/mm/proc-v7-3level.S b/arch/arm/mm/proc-v7-3level.S
> > index 5e5720e..7d16bbc 100644
> > --- a/arch/arm/mm/proc-v7-3level.S
> > +++ b/arch/arm/mm/proc-v7-3level.S
> > @@ -129,8 +129,7 @@ ENDPROC(cpu_v7_set_pte_ext)
> > .macro v7_ttb_setup, zero, ttbr0l, ttbr0h, ttbr1, tmp
> > ldr \tmp, =swapper_pg_dir @ swapper_pg_dir virtual address
> > cmp \ttbr1, \tmp, lsr #12 @ PHYS_OFFSET > PAGE_OFFSET?
> > - mrc p15, 0, \tmp, c2, c0, 2 @ TTB control egister
> > - orr \tmp, \tmp, #TTB_EAE
> > + mov \tmp, #TTB_EAE @ for TTB control egister
> > ALT_SMP(orr \tmp, \tmp, #TTB_FLAGS_SMP)
> > ALT_UP(orr \tmp, \tmp, #TTB_FLAGS_UP)
> > ALT_SMP(orr \tmp, \tmp, #TTB_FLAGS_SMP << 16)
> > --
> > 2.7.4
> >
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2017-06-10 10:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 2:39 Hoeun Ryu
2017-06-10 4:43 ` Hoeun Ryu
2017-06-10 10:19 ` Russell King - ARM Linux [this message]
2017-06-12 1:47 Hoeun Ryu
2017-07-03 8:18 ` Hoeun Ryu
2017-08-04 6:07 ` Hoeun Ryu
2017-08-04 10:04 ` Robin Murphy
2017-08-04 13:26 ` Hoeun Ryu
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=20170610101943.GW4902@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=hoeun.ryu@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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
all inboxes | Powered by JetHome®