Re: Read/Write migration entries: Implement correct behavior in copy_one_pte

On Wed, 19 Apr 2006, KAMEZAWA Hiroyuki wrote:

> BTW, do we manage page table under move_vma() in right way ?

I had a look at it and it seems to be done the right way. The ptl locks
are taken and the vma information is setup before the move. 
remove_migration_ptes() will find the page both in the old and the new 
vma.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Read/Write migration entries: Implement correct behavior in copy_one_pte
    • From: Christoph Lameter <[email protected]>
  • Re: Read/Write migration entries: Implement correct behavior in copy_one_pte
    • From: KAMEZAWA Hiroyuki <[email protected]>
  • Re: Read/Write migration entries: Implement correct behavior in copy_one_pte
    • From: Christoph Lameter <[email protected]>
  • Re: Read/Write migration entries: Implement correct behavior in copy_one_pte
    • From: KAMEZAWA Hiroyuki <[email protected]>

• Prev by Date: Re: [RFC][PATCH 11/11] security: AppArmor - Export namespace semaphore
• Next by Date: Re: [RFC] Netlink and user-space buffer pointers
• Previous by thread: Re: Read/Write migration entries: Implement correct behavior in copy_one_pte
• Next by thread: Read/Write migration entries: Make mprotect() convert write migration entries to read
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]