public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: buildroot@browserseal.com (Sasha Sirotkin)
To: linux-arm-kernel@lists.infradead.org
Subject: Question about ARM set_pte_ext
Date: Sat, 17 Apr 2010 10:44:15 +0300	[thread overview]
Message-ID: <4BC966CF.9040503@browserseal.com> (raw)

I'm still trying to understand the peculiarities of ARMv5 memory 
management...

I have a question about ARM set_pte_ext or armv3_set_pte_ext to be more 
specific.
In the following lines

    tst    r3, #L_PTE_USER            @ user?
    orrne    r2, r2, #PTE_SMALL_AP_URO_SRW

We are testing for L_PTE_USER not being set. Why not?

Another question is about S & R bits of CP15 register 1, which on ARMv5 
are used to control memory access in combination with AP bits. As 
changing S & R bits requires to reset the MMU, basically it is 
impossible to use them, if I wanted to configured a certain page to be, 
for instance, read-only for both kernel and user modes?

Thanks.

             reply	other threads:[~2010-04-17  7:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17  7:44 Sasha Sirotkin [this message]
2010-04-17 11:16 ` Question about ARM set_pte_ext Dmytro Milinevskyy

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=4BC966CF.9040503@browserseal.com \
    --to=buildroot@browserseal.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