Re: [ros-kernel] crash within MmOpenMemoryAreaByAddress

[<we...@cw...>]

Quoting Casper Hornstrup <ch...@us...>:
> 
> This seem like a big change to the memory manager, so if nobody objects,
> then I would like to flush my changes to the memory manager to support a
> modified page writer. Unfortunatly the system, in it's current state, 
> deadlocks when the balance manager is run so it has to be disabled for now. 
> This means that paging to disk will not work until I or someone else get this 
> fixed. With the balancer disabled, it runs fine. Okay to commit?
> 
I think it would be preferable to commit without known bugs. Why not post the
code to the list or commit to a seperate branch of the repository so more
people can help with debugging without having to break existing functionality.

Moreover I'm not sure that Harmutt Birr's suggestion is the best way to fix the
problem: I would prefer to special case the Mm{Unmap,Map}LockedPages function
rather than burden large parts of the memory manager with having to run at
DISPATCH_LEVEL. Firstly we could have a identity map of the first 256MB to
map one page, low memory reguests very fast (as NT does) and secondly a
dedicated region with the page tables already set up which can be 
guarded with a spinlock.