From: Christian Kandeler <christian.kandeler@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Question about backing store access rights
Date: Tue, 20 Feb 2007 10:07:05 +0000 [thread overview]
Message-ID: <200702201107.05662.christian.kandeler@hob.de> (raw)
Hello,
I hope that someone can enlighten me about how the mapping of a process' RSE
backing store page is supposed to work.
From what I can see, the area gets initialized in the ia64_init_addr_space()
function, where its vm_page_prot member is set to __P011, i.e. PAGE_READONLY,
which I assume is supposed to be changed on the first write access. However,
according to the IASDM, RSE stores always set ISR.w to zero on an
interruption, so the page fault handler will never know that it's dealing
with a write access. Consequently, processes should end up in an endless loop
of IR Data Access Rights faults. Why don't they? What am I missing here?
Thanks,
Christian
next reply other threads:[~2007-02-20 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 10:07 Christian Kandeler [this message]
2007-02-20 10:42 ` Question about backing store access rights Christian Kandeler
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=200702201107.05662.christian.kandeler@hob.de \
--to=christian.kandeler@hob.de \
--cc=linux-ia64@vger.kernel.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