search for: do_update_va_mapping

Hi, I am bit confused about the do_update_va_mapping call that dom0 makes in xen_ident_map_ISA() to map ffff8800000a0000 to mfn a0. The mfn belongs to DOMID_IO. Before the mfn is mapped, the l1 entry is not empty: 0000000139d08500: 00100001380a0027 After the mapping: 0000000139d08500: 00100000000a0467 as expected. However, the mfn 1380a0 still...

Hi, When I read the code of do_update_va_mapping, I find that it update the pte entry in the line page table by looking up the line page table via guest_map_l1e() : 2998 <http://lxr.xensource.com/lxr/source/xen/arch/x86/mm.c?a=x86_64#L2998> int do_update_va_mapping <http://lxr.xensource.com/lxr/ident?a=x86_64;i=do_update_va_mapping>(...

...4_13138-0.33 get_page_from_l1e 71812 4.6672 xen-syms-pae-3.0.4_13138-0.33 xen-syms-pae-3.0.4_13138-0.33 handle_exception 58634 3.8107 xen-syms-pae-3.0.4_13138-0.33 xen-syms-pae-3.0.4_13138-0.33 put_page_from_l1e 56301 3.6591 xen-syms-pae-3.0.4_13138-0.33 xen-syms-pae-3.0.4_13138-0.33 do_update_va_mapping 49543 3.2199 vmlinux-2.6.16.46-0.10-xenpae vmlinux-2.6.16.46-0.10-xenpae _spin_lock Domain 0, Prefork: CPU: Core 2, speed 2666.75 MHz (estimated) Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit mask of 0x00 (Unhalted core cycles) count 100000 samples % image...

...4_13138-0.33 get_page_from_l1e 71812 4.6672 xen-syms-pae-3.0.4_13138-0.33 xen-syms-pae-3.0.4_13138-0.33 handle_exception 58634 3.8107 xen-syms-pae-3.0.4_13138-0.33 xen-syms-pae-3.0.4_13138-0.33 put_page_from_l1e 56301 3.6591 xen-syms-pae-3.0.4_13138-0.33 xen-syms-pae-3.0.4_13138-0.33 do_update_va_mapping 49543 3.2199 vmlinux-2.6.16.46-0.10-xenpae vmlinux-2.6.16.46-0.10-xenpae _spin_lock Domain 0, Prefork: CPU: Core 2, speed 2666.75 MHz (estimated) Counted CPU_CLK_UNHALTED events (Clock cycles when not halted) with a unit mask of 0x00 (Unhalted core cycles) count 100000 samples % image...

...+ ? GNTUPDVA_prev_rw + : GNTUPDVA_prev_ro ); /* use return code to avoid nasty grant table * slow path in put_page_from_l1e -- caller * must handle ref count instead. */ @@ -2024,7 +2028,7 @@ int update_grant_va_mapping(unsigned lon int do_update_va_mapping(unsigned long va, - unsigned long val, + l1_pgentry_t val, unsigned long flags) { struct exec_domain *ed = current; @@ -2050,8 +2054,7 @@ int do_update_va_mapping(unsigned long v * the case of updating L2...

While working on a database scaling problem using a SAP database test suite we discovered that these enterprise level large shared memory databases are very heavy users of mprotect(), to the extent that the performance overhead in current Xenolinux impacts scaling beyond a few cpus quite badly. A single cpu run under Xen has a nominal impact, but scaling out to 8 cpus results in a performance of

...ll /* stack_switch */ + .long do_set_callbacks + .long do_ni_hypercall /* fpu_switch */ + .long do_sched_op_compat + .long do_ni_hypercall + .long do_ni_hypercall + .long do_ni_hypercall + .long do_ni_hypercall /* 10 */ + .long do_ni_hypercall + .long do_memory_op + .long do_multicall + .long do_update_va_mapping + .long do_set_timer_op /* 15 */ + .long do_event_channel_op + .long do_xen_version + .long do_console_io + .long do_physdev_op + .long do_grant_table_op /* 20 */ + .long do_vm_assist + .long do_ni_hypercall + .long do_restore_trap_frame + .long do_vcpu_op + .long do_ni_hypercall /* 25 */ + .long...

Hi, I just added 32GB memory in my system and wanted Xen to see that memory, so enabled PAE in xen0 and XenU. I did a make menuconfig in xen0 and xenU, then did a make in xen-unstable and a make install. Whilebooting this kernel, I get the above error PAE mode mismatch. I looked under xen/include/asm-x86/processor.h has #define X86_CR4_PAE defined and so does cpufeature.h have this defined.

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of

Hi all, this patch series makes the necessary changes to make sure that the current ARM hypercall ABI can be used as-is on 64 bit ARM platforms: - it defines xen_ulong_t as uint64_t on ARM; - it introduces a new macro to handle guest pointers, called XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to have size 8 bytes on aarch64); - it replaces all the occurrences of