search for: shadow_op

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

...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_access from guest_walk_tables) could be removed. Thanks for clarification. > >I think that in guest_walk_tables, you nee...

...ret = do_domctl(xc_handle, &domctl); - if ( ctxt_buf ) + if ( ctxt_buf ) unlock_pages(ctxt_buf, size); return (ret < 0 ? -1 : domctl.u.hvmcontext.size); @@ -338,8 +338,8 @@ int xc_shadow_control(int xc_handle, if ( stats ) memcpy(stats, &domctl.u.shadow_op.stats, sizeof(xc_shadow_op_stats_t)); - - if ( mb ) + + if ( mb ) *mb = domctl.u.shadow_op.mb; return (rc == 0) ? domctl.u.shadow_op.pages : rc; @@ -696,6 +696,79 @@ int xc_get_hvm_param(int handle, domid_t return rc; } +int xc_add_adom(int handle,...

...imulate 32-bit guest''s 2-level page-table. Signed-off-by: Chengyuan Li <chengyuan.li@intel.com> Signed-off-by: Xiaohui Xin <xiaohui.xin@intel.com> Signed-off-by: Jun Nakajima <jun.nakajima@intel.com> b/xen/arch/x86/shadow_guest32.c | 18 + b/xen/include/asm-x86/shadow_ops.h | 130 +++++++++ xen/arch/x86/Makefile | 2 xen/arch/x86/shadow.c | 516 ++++++++++++++++++++++++++++-------- xen/arch/x86/shadow_public.c | 93 +++++- xen/arch/x86/vmx.c | 22 + xen/include/asm-x86/page-guest32.h | 5 xen/include...

Hi, I''m doing my master research and I need to adapt remus code. Now... I wanna get the checkpoint size (memory + disk) on each period. Does someone know what function does this? I think some *fd *object''s function in remus code could just get the memory size. Does someone help me? Thanks _______________________________________________ Xen-devel mailing list

These two patches were originally part of the XSM series that I have posted, and remain prerequisites for that series. However, they are independent of the XSM changes and are a useful simplification regardless of the use of XSM. The Acked-bys on these patches were provided before rebasing them over the copyback changes in 26268:1b72138bddda, which had minor conflicts that I resolved. [PATCH

...--git a/xen/arch/arm/domctl.c b/xen/arch/arm/domctl.c index cb38e59..eb74225 100644 --- a/xen/arch/arm/domctl.c +++ b/xen/arch/arm/domctl.c @@ -93,6 +93,15 @@ long arch_do_domctl(struct xen_domctl *domctl, struct domain *d, xfree(c.data); } break; + case XEN_DOMCTL_shadow_op: + { + domain_pause(d); + ret = dirty_mode_op(d, &domctl->u.shadow_op); + domain_unpause(d); + + copyback = 1; + } + break; default: return -EINVAL; diff --git a/xen/arch/arm/mm.c b/xen/arch/arm/mm.c index bf13993..d5a0a11 100...

...*/ + uint64_t num; + /* IN/OUT variables. */ + XEN_GUEST_HANDLE(ulong) array; +}; +typedef struct xen_domctl_getpageframeinfo2 xen_domctl_getpageframeinfo2_t; +DEFINE_XEN_GUEST_HANDLE(xen_domctl_getpageframeinfo2_t); + + +/* + * Control shadow pagetables operation + */ +#define XEN_DOMCTL_shadow_op 10 + +/* Disable shadow mode. */ +#define XEN_DOMCTL_SHADOW_OP_OFF 0 + +/* Enable shadow mode (mode contains ORed XEN_DOMCTL_SHADOW_ENABLE_* flags). */ +#define XEN_DOMCTL_SHADOW_OP_ENABLE 32 + +/* Log-dirty bitmap operations. */ + /* Return the bitmap and clean internal copy f...

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not