This makes the linux dmapi match the irix dmapi behavior. We ignore whether
or not the user is reading or writing the pages, and instead just look at what
they're _capable_ of doing to the file and generate a dmapi event based on
that.
This is a brain-dead way of doing things, but maybe slightly less brain-dead
than what we have on irix, and it will hold things over until I can spend more
time on doing it right.
Date: Fri Oct 26 08:14:10 PDT 2001
Workarea: clink-eth.americas.sgi.com:/data/clink/a67/roehrich/2.4.x-xfs
The following file(s) were checked into:
bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs
Modid: 2.4.x-xfs:slinx:105510a
linux/mm/mprotect.c - 1.17
- If protection is being changed from read to write, send a dmapi event.
linux/include/linux/fs.h - 1.130
- Add dmapi_map_event method to struct file_operations.
linux/fs/xfs/linux/xfs_file.c - 1.49
- -Add linvfs_dmapi_map_event(). Decides if mmap activity requires a
read
or write event to dmapi, sends the event.
-Make linvfs_generic_file_mmap() call the above.
|