Re: pmap_remap_pages and protection (save/restore, part 1)

To: jdev%panix.com@localhost
Subject: Re: pmap_remap_pages and protection (save/restore, part 1)
From: YAMAMOTO Takashi <yamt%mwd.biglobe.ne.jp@localhost>
Date: Thu, 08 Sep 2005 11:07:49 +0900

> I notice that some of the relevant parts of pmap_remap_pages appear to
> have been copied from pmap_enter, which has a "prot" argument as well
> as the "flags" one.  Is there any reason why it shouldn't have one?

because our current implementation of the ioctl is a hack.

it isn't straightforward to handle faults on the mapping correctly
within our vm structure because the api has very linux-vm centric design.

YAMAMOTO Takashi

Follow-Ups:
- Re: pmap_remap_pages and protection (save/restore, part 1)
  - From: Jed Davis

References:
- pmap_remap_pages and protection (save/restore, part 1)
  - From: Jed Davis

Prev by Date: IOCTL_PRIVCMD_GET_MACH2PHYS_START_MFN is a read, not a write. (save/restore, part 2)
Next by Date: IOCTL_PRIVCMD_MMAPBATCH (save/restore, part 3)
Previous by Thread: pmap_remap_pages and protection (save/restore, part 1)
Next by Thread: Re: pmap_remap_pages and protection (save/restore, part 1)
Indexes:

Home | Main Index | Thread Index | Old Index