Puthiyaparambil, Aravindh
2006-Dec-15 21:43 UTC
[Xen-devel] Auto translated physmap feature
If you use the auto translated physmap feature for a DomU, I understand that the p2m conversion is done by Xen and not by referencing the p2m table that is passed by the domain builder to the DomU. So with auto translated physmap, the p2m table for the DomU lives in the Xen space and not in the DomU space? Is it possible to use this feature in driver domains? I tried using this feature by adding "features ''auto_translated_physmap''" in the DomU config file. The DomU dies with the following error. Is this a known issue? I am on Xen x86_64 change-set 12898:37141c3a3d39. Thanks, Aravindh Puthiyaparambil Xen Development Team Unisys, Tredyffrin PA (XEN) mtrr: type mismatch for f0000000,1000000 old: write-back new: write-combining (XEN) sh error: shadow_remove_all_mappings(): can''t find all mappings of mfn 204971: c=00000001 t=00000000 (XEN) Unhandled page fault in domain 1 on VCPU 0 (ec=0001) (XEN) Pagetable walk from ffff8000000060d8: (XEN) L4[0x100] = 0000000063d84063 5555555555555555 (XEN) L3[0x000] = 0000000063d85067 5555555555555555 (XEN) L2[0x000] = 0000000063d86067 5555555555555555 (XEN) L1[0x006] = 0000000063d7d067 5555555555555555 (XEN) domain_crash_sync called from entry.S (XEN) Domain 1 (vcpu#0) crashed on cpu#3: (XEN) ----[ Xen-3.0-unstable x86_64 debug=y Not tainted ]---- (XEN) CPU: 3 (XEN) RIP: e033:[<ffffffff803d4043>] (XEN) RFLAGS: 0000000000000246 CONTEXT: guest (XEN) rax: ffff800000000000 rbx: 0000000000000000 rcx: 0000000000000023 (XEN) rdx: 0000000000000c1b rsi: 0000000000000000 rdi: ffffffff80106000 (XEN) rbp: ffffffff803ae000 rsp: ffffffff803c7f60 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: ffffffff80105000 r11: 0000000000001000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000026b0 (XEN) cr3: 0000000063c83000 cr2: ffff8000000060d8 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff803c7f60: (XEN) 0000000000000023 0000000000001000 0000000000000001 ffffffff803d4043 (XEN) 000000000000e030 0000000000010246 ffffffff803c7fa0 000000000000e02b (XEN) 0000000000000023 ffffffff80111be0 0000000000000000 0000000000000000 (XEN) 0000000000000000 ffffffff803c90d8 ffff800000000000 ffff804000000000 (XEN) 00000007ffffffff 0000000000000000 0000000000000000 0000000000000000 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 15/12/06 21:43, "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@unisys.com> wrote:> If you use the auto translated physmap feature for a DomU, I understand > that the p2m conversion is done by Xen and not by referencing the p2m > table that is passed by the domain builder to the DomU. So with auto > translated physmap, the p2m table for the DomU lives in the Xen space > and not in the DomU space? Is it possible to use this feature in driver > domains?There''s no support right now for hooking mmio memory ranges into the domU''s pseudophysical address space, so a driver domain would not be able to access mmio device resources. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel