search for: guest_map_l1

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>(unsigned long va, u64 <http://lxr.xensource.com/lxr/ident?a=x86_64;i=u64> val64, 2999 <http://lxr.xens...

1: correct LDT checks 2: add address validity check to guest_map_l1e() 3: use {rd,wr}{fs,gs}base when available 4: check for canonical address before doing page walks Signed-off-by: Jan Beulich <jbeulich@suse.com>

Just found this patch in house which I thought sent out already. :-) Still one thing remaining is to special case for UP guest which suffers overhead from this change... ---- Remove lock on first guest table walk Existing shadow fault path grabs big lock before walking guest tables, to ensure consistency with shadow content lest concurrent change from other vcpu in a bad OS. But this lock

We have found a critical problem with the XEN 3.1 release (for those who are running 15-20 VMs on a single server). We are using the official XEN 3.1 release on a rackable server (Dual-Core AMD Opteron, 8GB RAM). The problem we are seeing is that intermittently vifs fail to work properly in VMs after we create around 15-17 VMs on our server (all running at the same time, created one by

...move lock on guest table walk >From: Tim Deegan >Sent: 2008年2月21日 22:13 >Hi, > >So, the idea seems sound, and avoids the shadow lock altogether on a >bunch more pagefaults, which is nice. > >I think that since PV pagetables are guaranteed to be read-only above >l1e, the guest_map_l1e and guest_get_eff_l1e functions can be >allowed to >drop the shadow lock and call guest_walk_tables with shadow_op == 0. >That would mean that there are no callers left setting shadow_op to 1, >and then the shadow_op argument (and the whole mechanism for calling >remove_write_acces...

Hi Keir: These two patches remove the need for netloop by performing the copying in netback and only if it is necessary. The rationale is that most packets will be processed without delay allowing them to be freed without copying at all. So instead of copying every packet destined to dom0 we''ll only copy those that linger longer than a specified amount of time (currently 0.5s). As it