From: "Chris Friesen" <cfriesen@nortel.com>
To: linuxppc-dev@ozlabs.org
Subject: question on modifying pte entries
Date: Wed, 31 Oct 2007 13:45:07 -0600 [thread overview]
Message-ID: <4728DB43.1060205@nortel.com> (raw)
Hi all,
We've got some kernel code that monitors which pages have been dirtied
by an application.
The pages are locked in memory, and the system has no swap. Initially
we mark the pages clean using ptep_clear_flush_dirty(), then when
requested by the app we scanning through the pages and check the dirty
bit using pte_dirty(). If it's dirty we store the address and then mark
it clean using the same function as above. The above is all done while
holding both mm->mmap_sem and mm->page_table_lock.
This worked fine in 2.6.10 but now in 2.6.14 it's giving us problems.
Periodically we'll get a page that we know has been dirtied, but it
doesn't get detected as such. It appears that once this occurs, that
page will never again be detected as dirty.
Does anyone have any ideas what may be happening? Were there any
changes in the page table area other than moving to 4-level mappings?
Anyone aware of any missing tlb flushes that were fixed later?
Thanks,
Chris
next reply other threads:[~2007-10-31 20:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 19:45 Chris Friesen [this message]
2007-11-01 4:37 ` question on modifying pte entries Benjamin Herrenschmidt
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=4728DB43.1060205@nortel.com \
--to=cfriesen@nortel.com \
--cc=linuxppc-dev@ozlabs.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).