lkml.org 
[lkml]   [2009]   [Apr]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] [10/16] POISON: Use bitmask/action code for try_to_unmap behaviour
On Tue, 7 Apr 2009, Andi Kleen wrote:

> +
> +enum ttu_flags {
> + TTU_UNMAP = 0, /* unmap mode */
> + TTU_MIGRATION = 1, /* migration mode */
> + TTU_MUNLOCK = 2, /* munlock mode */
> + TTU_ACTION_MASK = 0xff,
> +
> + TTU_IGNORE_MLOCK = (1 << 8), /* ignore mlock */


Ignoring MLOCK? This means we are violating POSIX which says that an
MLOCKed page cannot be unmapped from a process? Note that page migration
does this under special pte entries so that the page will never appear to
be unmapped to user space.

How does that work for the poisoning case? We substitute a fresh page?



\
 
 \ /
  Last update: 2009-04-07 23:27    [from the cache]
©2003-2011 Jasper Spaans