Global anchor for page_t lists is the symbol  memsegs, which 
describes the system's set of physically contiguous physical pages
("page frames"):
http://src.illumos.org/source/xref/illumos-gate/usr/src/uts/common/vm/vm_page.c

defined http://src.illumos.org/source/xref/illumos-gate/usr/src/uts/common/vm/page.h#1114

Observe how the page arrays are traversed in search of a page_t corresponding
to a physical page (referenced as "page frame number", i.e. 
physical_address/page_size), lines 5815--5929. 

In "mdb -k":

::memseg_list

*memsegs::print "struct memseg"

*memsegs::list "struct memseg" next | ::print "struct memseg"

To each of the "struct memseg".pages member we can apply
both an array and a list traversal. Observe that the pages
are allocated one after another, each 0x50 bytes, which is, of
course, ::sizeof page_t

The top of the memseg list/array, explained in Fig. 10.4 p. 510: 

as array of 1000 contiguous page_t structures:

*memsegs::print "struct memseg" pages | ::array page_t 1000 

as a linked list:

*memsegs::print "struct memseg" pages | ::list page_t p_next

For any of the page_t struct addresses output by the above:

<addr>::print page_t p_vnode p_vnode->v_path p_offset 

will print the "identity" vnode (with the filepath is any) and the offset 
associated with the page.

You can further filter the output with !grep <regexp>  
or specify the traversal order by ::array or ::list .

For example, 

*memsegs::print "struct memseg" pages | ::array page_t 1000 | ::print page_t p_vnode p_vnode->v_path p_offset !grep -C 1 UTF-8 

will display all the mappings of the library that deals with UNICODE character encodings
on the system (see "man grep" for the useful -C <lines_of_context_around_match> option)

<vnode_addr>::whereopen is supposed to give the proc_t addresses for the processes 
  which have vnode_addr opened.

Suggestion: start a process whose pages are easily recognizable (e.g.,
"vim hello.c" for an existing file "hello.c"), and find the respective
physical pages allocated to hold that process' memory. mmaped file(s)
and buffers.


Observe the (vnode,offset) hashing algorith at
http://src.illumos.org/source/xref/illumos-gate/usr/src/uts/common/vm/page.h#590

and its matching hashing algorithm for locating page hash collision list locks,
line 636.