search for: phys2mach

...percall. So then is p==m in dom0 (and driver domains) an unacceptable design alternative for (non-x86) Xen architectures? If it is acceptable, then the question remains: > So the question becomes: Should Xen drivers be made more portable > to accommodate architectures where a guest-visible phys2mach table > is NOT required for paravirtualizing the architecture? Or should > Linux code for each architecture that is ported to Xen be modified > to utilize data structures that are only really necessary for x86? Thanks, Dan _______________________________________________ Xen-devel mailin...

>From: Keir Fraser >Sent: 2005年12月30日 4:34 > >On 29 Dec 2005, at 18:51, Magenheimer, Dan (HP Labs Fort Collins) wrote: > >> So then is p==m in dom0 (and driver domains) an unacceptable design >> alternative for (non-x86) Xen architectures? If it is acceptable, >> then the question remains: > >I think *that* is the critical question here. My feeling is that

...xb3686890 elf_load_binary: phdr 1 at 0x0xb3687000 -> 0x0xb3701b64 xc_dom_alloc_segment: ramdisk : 0xc1439000 -> 0xc14d9000 (pfn 0x1439 + 0xa0 pages) xc_dom_pfn_to_ptr: domU mapping: pfn 0x1439+0xa0 at 0xb32e7000 xc_dom_do_gunzip: unzip ok, 0x3b899 -> 0x9fc10 xc_dom_alloc_segment: phys2mach : 0xc14d9000 -> 0xc14f9000 (pfn 0x14d9 + 0x20 pages) xc_dom_pfn_to_ptr: domU mapping: pfn 0x14d9+0x20 at 0xb5860000 xc_dom_alloc_page : start info : 0xc14f9000 (pfn 0x14f9) xc_dom_alloc_page : xenstore : 0xc14fa000 (pfn 0x14fa) xc_dom_alloc_page : console : 0xc14fb000...

...x0x7fdeca0dd000 xc: detail: elf_load_binary: phdr 1 at 0x0x7fdeca0dd000 -> 0x0x7fdeca1460e8 xc: detail: elf_load_binary: phdr 2 at 0x0x7fdeca147000 -> 0x0x7fdeca1597c0 xc: detail: elf_load_binary: phdr 3 at 0x0x7fdeca15a000 -> 0x0x7fdeca1cd000 domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0xffffffff81b08 000 -> 0xffffffff824cc000 (pfn 0x1b08 + 0x9c4 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x1b08+0x9c4 at 0x7fdec91c1000 domainbuilder: detail: xc_dom_alloc_page : start info : 0xffffffff824cc 000 (pfn 0x24cc) domainbuilder: detail: xc_dom_alloc...

...(pfn 0x16fa + 0x1a1d pages) domainbuilder: detail: xc_dom_malloc : 156 kB domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x16fa+0x1a1d at 0x7f3a57802000 domainbuilder: detail: xc_dom_do_gunzip: unzip ok, 0x8dcc4c -> 0x1a1c010 domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0xffffffff83117000 -> 0xffffffff83197000 (pfn 0x3117 + 0x80 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x3117+0x80 at 0x7f3a5cd6f000 domainbuilder: detail: xc_dom_alloc_page : start info : 0xffffffff83197000 (pfn 0x3197) domainbuilder: detail: xc_dom_alloc_pag...

I''m unable to start xl console on latest xen-unstable (build with commit 8e0da8c07f4f80e14314977a11f738bd74a5b62b). > xl -vvv console sid > xenconsole: Could not read tty from store: No such file or directory I also tried "xl create -c", and it shows console from pygrub but when the "xl create" reaches the end I got the same error: > xenconsole: Could not

...l: xc_dom_alloc_segment: kernel : 0x0 -> 0x9a0000 (pfn 0x0 + 0x9a0 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x0+0x9a0 at 0x7f18be2e9000 xc: detail: elf_load_binary: phdr 0 at 0x0x7f18be2e9000 -> 0x0x7f18bec88f60 domainbuilder: detail: xc_dom_alloc_segment: phys2mach : 0x9a0000 -> 0xaa0000 (pfn 0x9a0 + 0x100 pages) domainbuilder: detail: xc_dom_pfn_to_ptr: domU mapping: pfn 0x9a0+0x100 at 0x7f18be1e9000 domainbuilder: detail: xc_dom_alloc_page : start info : 0xaa0000 (pfn 0xaa0) domainbuilder: detail: xc_dom_alloc_page : xenstore : 0xaa1000...