linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: bad pmd
Date: Wed, 29 Dec 2010 12:51:23 +0800	[thread overview]
Message-ID: <AANLkTimatgB15ZLyD_ryVOSfg4s6pHUa0hmRZ9DAmUXP@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinP=1opPSDMULHn9DDBMVfT15RaZ0K_WAh7JJuz@mail.gmail.com>

On Tue, Dec 14, 2010 at 11:08 PM, Matt Reimer <mreimer@sdgsystems.com> wrote:
> On Wed, Dec 8, 2010 at 9:02 AM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
>> On Tue, Dec 07, 2010 at 12:26:45PM -0500, Aric D. Blumer wrote:
>>> Matt Reimer and I believe we have found what is going on here. ?I've put
>>> in a fix (no failures yet), but I wanted to bounce it off anyone interested.
>>>
>>> The PXA platform does not use the "bad pmd" mapping that Russell
>>> describes above under normal circumstances, but the PXA resume code
>>> (arch/arm/mach-pxa/sleep.S) does on resume:
>>
>> Good find.
>>
>>> I'm using the patch below as a fix for now, but it's hard to know what
>>> registers are available. ?Might be better to just mask it off the lower
>>> bits in r1 again.
>>>
>>> ? ? ? ? @ Let us ensure we jump to resume_after_mmu only when the mcr above
>>> ? ? ? ? @ actually took effect. ?They call it the "cpwait" operation.
>>> - ? ? ? mrc ? ? p15, 0, r1, c2, c0, 0 ? ? ? ? ? @ queue a dependency on CP15
>>> - ? ? ? sub ? ? pc, r2, r1, lsr #32 ? ? ? ? ? ? @ jump to virtual addr
>>> + ? ? ? mrc ? ? p15, 0, r0, c2, c0, 0 ? ? ? ? ? @ queue a dependency on CP15
>>> + ? ? ? sub ? ? pc, r2, r0, lsr #32 ? ? ? ? ? ? @ jump to virtual addr
>>
>> I don't see anything wrong with this. ?Any PXA people want to ack this?

Me neither.

Acked-by: Eric Miao <eric.y.miao@gmail.com>

>
> This patch fixes the problem for us. We have yet to see a failure with
> this patch applied.
>
> Eric, do you concur that this is a proper fix?
>

This patch is good. Thanks for figuring this out. My bad replying so
late.

Russell,

Still time for this fix to get into .37?

> Matt
>

  reply	other threads:[~2010-12-29  4:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 19:54 bad pmd Aric D. Blumer
2010-12-01 20:14 ` Russell King - ARM Linux
2010-12-02  2:35   ` Aric D. Blumer
2010-12-07 17:26     ` Aric D. Blumer
2010-12-08 14:02       ` Russell King - ARM Linux
2010-12-14 15:08         ` Matt Reimer
2010-12-29  4:51           ` Eric Miao [this message]
2010-12-29 16:23             ` Matt Reimer
2011-01-02 23:51               ` Russell King - ARM Linux
2010-12-29 16:18 ` [PATCH] [ARM] pxa: fix page table corruption on resume Matt Reimer
2011-01-03 15:47   ` Eric Miao

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=AANLkTimatgB15ZLyD_ryVOSfg4s6pHUa0hmRZ9DAmUXP@mail.gmail.com \
    --to=eric.y.miao@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 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).