Re: Fpage mapping in L4 Pistachio
Katsumi Maruyama <[email protected]>
| Newsgroups | gmane.comp.micro-kernel.l4.l4ka.general |
|---|---|
| Message-ID | <[email protected]> |
Dear Espen Skoglund:
Than you for your help.
I tried some KDB commands.
(I am not familiar wth the KDB. A KDB manual is wanted.)
------ Test condition ----
The test condition is as follows:
[1] Mapper
mapper<a26820-a28000, a28000, 10000>
This means:
Buffer ia located at [a26820-a28000]. (size is 6113)
Mapper Flexpage : <a28000, 10000>
(a26820 is very delicated address !?)
[2] Mappee
(My mappee assigns the idle mappee fpage at 1G + 1M*n of 1M window size )
mappee<40606820-40608000, 40600000, 1000000>
Buffer is to be accessible at: [40606820-40608000] (6113 bytes)
Mappee flex page: <40600000, 1000000>
========== KDB results =============
Followings are KDB results,
just after receiveing mapping IPC in mappee.
------- d command --------
d
>memdump 40606820 ######## ######## ######## ########
.....
===> Expecting pages seem not mapped.
---- p command ------------
> ptab
.......
40400000 [0b44a027]: tree=fb44a000
40500000 .............
40501000 ............
40600000 [0117a007]: phys=0117a000 map=fb440568 4KB rw~ (~~~) user WB
40601000 [0117b007]: phys=0117b000 map=fb440eec 4KB rw~ (~~~) user WB
...........
40604000 [0117e007]: phys=0117e000 map=fb440f10 4KB rw~ (~~~) user WB
/***** Entries 40605000-406ff000 do not apper; ********/
40700000 [011bd005]: phys=011bd000 map=fb440544 4KB rw~ (~~~) user WB
40701000 ....................
40702000 ....................
===> Expected pages 40605000-406ff000 seem not apper.
--- m command --------------
> mdb
Address [0x0] 0117e000
01000000: 4MB [root] (f012c010)
0117e000: 4KB [map] (fb41d5f8)
[1] space=f0138000 ...
[2] space=fb426000 ....
[3] space=f4b18000 vaddr=40604000 pgent=fb44a818 (fb440f10)
>[Katsumi Maruyama]
>
>
>>>And the xbuf[] array should now be accessible at address 0x40006820 of
>>>mappee. Is this not happening?
>>>
>>>
>>>
>>>
>>I expected the mapping at 0x40006820, but it seemed not-mapped.
>>KDB d command answered:
>>d 0x40006820
>>
>>
>>>memdump
>>>
>>>
>>Dump address [0x0]: 0x40006820
>>0x40006820 ######## ######## ######## ########
>>.....
>>
>>
>
>Try dumping the page table of the mapper ('p' in kdb). Also, try
>dumping the mapping database for the page frame in question ('m' in
>kdb I think, and provide the physical address of the page).
>
> eSk
>
>
Thank you for your consideration.
K. Maruyama