mirror of
https://github.com/reactos/reactos.git
synced 2025-05-19 17:14:32 +00:00
e806d16b06
Currently, our CcMapData() behavior (same goes for CcPinRead()) is broken and is the total opposite of what Windows kernel does. By default, the later will let you map a view in memory without even attempting to bring its data in memory. On first access, there will be a fault and memory will be read from the hardware and brought to memory. If you want to force read on mapping/pinning, you have to set the MAP_NO_READ (or PIN_NO_READ) flag where kernel will fault on your behalf (hence the need for MAP_WAIT/PIN_WAIT). On ReactOS, by default, on mapping (and thus pinning), we will force a view read so that data is in memory. The way our cache memory is managed at the moment seems not to allow to fault on invalid access and if we don't force read, the memory content will just be zeroed. So trying to match Windows behavior, by default, now CcMapData() will enforce the MAP_NO_READ flag and warn once about this behavior change. |
||
|---|---|---|
| .. | ||
| cacheman.c | ||
| copy.c | ||
| fs.c | ||
| lazywrite.c | ||
| mdl.c | ||
| pin.c | ||
| view.c | ||