Hi all, while investigating ways to access the auxillary vector, I found that we currently don't deal correctly with struct ps_strings in 32bit compat. This structure is placed by the kernel into the initial stack and referenced in userland by __ps_strings. It is used by setproctitle(3) and therefore e.g. by programs that want to include a status report in the ps(1) output. This naturally works only by chance, if at all in compat32. How do we want to deal with it? Variant 1: Leave it as ...

First step would be to start with populating the single, MI "phys_space_arena" and manage physical address "space". (This needs vmem(9) to be bootstrapped very early.) If this is done, and with my vm_physseg'ification, lots of MD code would be cleaned up.

I take silence as "no objection". -- Masao Uebayashi / Tombi Inc. / Tel: +81-90-9141-4635

This would be easy for cdevs if vm_physseg is allocated; cdev device pager returns the vm_physseg back to the fault handler. UVM can know if the faulting page is continugous physically or virtually Typical vnode lookup done in fault handling is: vaddr_t -> vm_map_entry -> uobj -> vm_page -> vm_physseg -> vm_page_md As I already explained many times, you need only 2 kind of lookups: vm_page -> vm_physseg + off vm_physseg + off -> vm_page_md (pvh)