linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@oracle.com (santosh shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] ARM: re-implement physical address space switching
Date: Wed, 15 Apr 2015 10:27:55 -0700	[thread overview]
Message-ID: <552E9F9B.2040400@oracle.com> (raw)
In-Reply-To: <20150415120738.GD2866@leverpostej>

On 4/15/2015 5:07 AM, Mark Rutland wrote:
> Hi,
>
[..]

>>>>> +ENTRY(lpae_pgtables_remap_asm)
>>>>> +       stmfd   sp!, {r4-r8, lr}
>>>>> +
>>>>> +       mrc     p15, 0, r8, c1, c0, 0           @ read control reg
>>>>> +       bic     ip, r8, #CR_M                   @ disable caches and MMU
>>>>> +       mcr     p15, 0, ip, c1, c0, 0
>>>>> +       dsb
>>>>> +       isb
>>>>
>>>> Shouldn't the DSB be between the STMFD and the MCR (given the SP doesn't
>>>> point to an idmap/physical address)?
>>>>
>>>> I don't see why we need a DSB after the write to the SCTLR.
>>>>
>> dsb can be moved up after stmfd but leaving as above should be fine
>> as well.
>
> I don't think that it's safe to leave it where it is. Currently the
> STMFD could be reordered w.r.t. the cp15 accesses, and hence the write
> may occur with translation disabled (and would go to the wrong physical
> address).
>
> We need to ensure that the STMFD is executed before the MCR potentially
> changes the execution context. The DSB will ensure that in addition to
> ensuring completion of the write (i.e. it isn't left sat in a write
> buffer).
>
I see your point. Thanks for expanding it.

Regards,
Santosh

  reply	other threads:[~2015-04-15 17:27 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08  9:44 [PATCH 0/7] Fix Keystone 2 physical address switch Russell King - ARM Linux
2015-04-08  9:45 ` [PATCH 1/6] ARM: keystone2: move platform notifier initialisation into platform init Russell King
2015-04-13 18:57   ` santosh shilimkar
2015-04-08  9:45 ` [PATCH 2/6] ARM: keystone2: move update of the phys-to-virt constants into generic code Russell King
2015-04-08 14:56   ` Grygorii.Strashko@linaro.org
2015-04-08 18:00     ` Russell King - ARM Linux
2015-04-09 14:51       ` Grygorii.Strashko@linaro.org
2015-04-09 15:49         ` Russell King - ARM Linux
2015-04-09 16:15           ` Grygorii.Strashko@linaro.org
2015-04-08 19:19     ` Russell King - ARM Linux
2015-04-13 19:02   ` santosh shilimkar
2015-04-08  9:45 ` [PATCH 3/6] ARM: keystone2: move address space switch printk to " Russell King
2015-04-13 19:02   ` santosh shilimkar
2015-04-08  9:45 ` [PATCH 4/6] ARM: keystone2: rename init_meminfo to pv_fixup Russell King
2015-04-13 19:03   ` santosh shilimkar
2015-04-08  9:45 ` [PATCH 5/6] ARM: re-implement physical address space switching Russell King
2015-04-08 14:34   ` Thomas Petazzoni
2015-04-08 17:27     ` santosh shilimkar
2015-04-08 18:10     ` Russell King - ARM Linux
2015-04-08 17:36   ` Mark Rutland
2015-04-08 17:55     ` Russell King - ARM Linux
2015-04-13 19:11       ` santosh shilimkar
2015-04-15 12:07         ` Mark Rutland
2015-04-15 17:27           ` santosh shilimkar [this message]
2015-04-23 11:24             ` Mark Rutland
2015-05-06 10:18               ` Russell King - ARM Linux
2015-05-06 10:37                 ` Mark Rutland
2015-05-06 11:33                   ` Russell King - ARM Linux
2015-05-06 15:33                     ` Mark Rutland
2015-05-06 15:50                       ` Russell King - ARM Linux
2015-05-06 16:14                         ` Mark Rutland
2015-05-06 16:24                           ` Will Deacon
2015-04-08  9:45 ` [PATCH 6/6] ARM: cleanup early_paging_init() calling Russell King
2015-04-13 19:13   ` santosh shilimkar
2015-04-08 17:21 ` [PATCH 0/7] Fix Keystone 2 physical address switch santosh shilimkar
2015-04-09 16:21   ` Russell King - ARM Linux
2015-04-09 16:35     ` santosh shilimkar

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=552E9F9B.2040400@oracle.com \
    --to=santosh.shilimkar@oracle.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).