On Tue, 2010-04-13 at 10:57 -0700, Roland Dreier wrote:
quoted text > Are those system calls the only possible way that virtual to physical
> mappings can change? Can't page migration or something like that
> potentially affect things? And even if you did have hooks into every
> system call that mattered (keep in mind that relying on glibc is not
> enough, since an MPI application may not use glibc) would decoding them
> and figuring out what happened really be preferable to a single event
> type that tells you exactly what address range was affected?
Yeah, virtual<->physical maps can change through swapping, page
migration, memory compaction, huge-page aggregation (the latter two not
yet being upstream).
Even mlock() doesn't pin virtual<->physical maps.
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: [PATCH] ummunotify: Userspace support for MMU notifica ... , Peter Zijlstra , (Tue Apr 13, 11:02 am)