search for: mem_ev

The following two patches allow the parallel use of memsharing, xenpaging and xen-access by using an independent ring buffer for each feature. Please review. v2: - update mem_event_check_ring arguments, check domain rather than domain_id - check ring_full first because its value was just evaluated - check if ring buffer is initialized before calling mem_access_domctl/mem_paging_domctl Olaf tools/libxc/Makefile | 2 tools/libxc/xc_mem_access.c...

...sig) { @@ -167,9 +169,68 @@ int xc_wait_for_event_or_timeout(xc_inte return -errno; } +int xenaccess_teardown(xc_interface *xch, xenaccess_t *xenaccess) +{ + int rc; + + if ( xenaccess == NULL ) + return 0; + + /* Tear down domain xenaccess in Xen */ + if ( xenaccess->mem_event.ring_page ) + munmap(xenaccess->mem_event.ring_page, PAGE_SIZE); + + if ( mem_access_enable ) + { + rc = xc_mem_access_disable(xenaccess->xc_handle, + xenaccess->mem_event.domain_id); + if ( rc != 0 ) + { + E...

Hello, I''m interested in using the mem_event API (or it''s LibVMI wrapper), but I''m interested in capturing write events anywhere in a domU guest''s memory, _and_ not just once for each page write, but every time a page is being written to. To this end, I''ve looked at the xen-access.c example, where at...

Add the new MEM_EVENT_REASON_MSR event type. Works similarly to the other register events, except event.gla always contains the MSR address (in addition to event.gfn, which holds the value). MEM_EVENT_REASON_MSR does not honour the HVMPME_onchangeonly bit, as doing so would complicate the hvm_msr_write_intercept() sw...

Hello, assuming that the VCPU is paused while waiting for userspace to respond to a page fault mem_event, and userspace calls libxc''s xc_domain_hvm_getcontext_partial(... CPU ...) and tries to inspect RIP, is this a safe thing to do? Is RIP''s value guaranteed to be safe to inspect in this context? Thanks, Razvan Cojocaru

Add the new MEM_EVENT_REASON_MSR event type. Works similarly to the other register events, except event.gla always contains the MSR type (in addition to event.gfn, which holds the value). Signed-off-by: Razvan Cojocaru <rzvncj@gmail.com> Acked-by: Tim Deegan <tim@xen.org> diff -r b04de677de31 -r e33d3d3...

...+ case EMLINK: + ERROR("xenpaging not supported while iommu passthrough is enabled"); break; case EXDEV: ERROR("xenpaging not supported in a PoD guest"); diff -r 80653c8ea1d1 -r 34d982818550 xen/arch/x86/mm/mem_event.c --- a/xen/arch/x86/mm/mem_event.c +++ b/xen/arch/x86/mm/mem_event.c @@ -564,10 +564,11 @@ int mem_event_domctl(struct domain *d, x break; /* No paging if iommu is used */ - rc = -EXDEV; + rc = -EMLINK; if ( unlikely(need_iommu(...

...t). Not sure at all what to do next. Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org> Signed-off-by: Adin Scannell <adin@scannell.ca> xen/drivers/passthrough/iommu.c | 2 + xen/arch/x86/mm/p2m-pt.c | 56 ++++++++++++++++++++++++++++------------ xen/arch/x86/mm/mem_event.c | 7 +++- xen/arch/x86/mm/mem_sharing.c | 7 +++++ 4 files changed, 53 insertions(+), 19 deletions(-)

This is a patch repairing a regression in code previously functional in 4.1.x. It appears that, during some refactoring work, calls to hvm_memory_event_cr3 and hvm_memory_event_cr4 were lost. These functions were originally called in mov_to_cr() of vmx.c, but the commit http://xenbits.xen.org/hg/xen-unstable.hg/rev/1276926e3795 abstracted the original code into generic functions up a level in

...98.china.huawei.com # Date 1329462865 -28800 # Node ID 9fd12f919ddbd15927117eff42149664dba698ca # Parent b75664e5390583c5d2075c82a14245bc941b3aaf x86/mm: Make sure the event channel is released accurately In xenpaging source code,there is an interdomain communication between dom0 and domU. In mem_event_enable(),the function alloc_unbound_xen_event_channel() allocates a free port for domU, and then it will be bound with dom0. When xenpaging tears down,it just frees dom0''s event channel port by xc_evtchn_unbind(), leaves domU''s port still occupied. So we add the patch to fr...

...te( spin_lock_init(&d->shutdown_lock); d->shutdown_code = -1; + spin_lock_init(&d->pbuf_lock); + err = -ENOMEM; if ( !zalloc_cpumask_var(&d->domain_dirty_cpumask) ) goto fail; @@ -286,6 +288,10 @@ struct domain *domain_create( d->mem_event = xzalloc(struct mem_event_per_domain); if ( !d->mem_event ) goto fail; + + d->pbuf = xzalloc_array(char, DOMAIN_PBUF_SIZE); + if ( !d->pbuf ) + goto fail; } if ( (err = arch_domain_create(d, domcr_flags)) != 0 ) @@ -318,6 +324,...

...te( spin_lock_init(&d->shutdown_lock); d->shutdown_code = -1; + spin_lock_init(&d->pbuf_lock); + err = -ENOMEM; if ( !zalloc_cpumask_var(&d->domain_dirty_cpumask) ) goto fail; @@ -286,6 +288,10 @@ struct domain *domain_create( d->mem_event = xzalloc(struct mem_event_per_domain); if ( !d->mem_event ) goto fail; + + d->pbuf = xzalloc_array(char, DOMAIN_PBUF_SIZE); + if ( !d->pbuf ) + goto fail; } if ( (err = arch_domain_create(d, domcr_flags)) != 0 ) @@ -318,6 +324,...

...be optionally passed in the prep operation, and having the hypervisor memcpy from that buffer into the newly prepped page before promoting the gfn type. Second patch is a tools patch, cc''ed maintainers. Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org> xen/arch/x86/mm/mem_event.c | 2 +- xen/arch/x86/mm/mem_paging.c | 2 +- xen/arch/x86/mm/p2m.c | 52 +++++++++++++++++++++++++++++++++++++++++-- xen/include/asm-x86/p2m.h | 2 +- xen/include/public/domctl.h | 8 +++++- tools/libxc/xc_mem_event.c | 4 +- tools/libxc/xc_mem_paging.c | 23 ++++++++...

...found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ changeset: 24885:0c3d19f40ab1 tag: tip user: Olaf Hering <olaf@aepfle.de> date: Mon Feb 20 22:16:32 2012 +0100 mem_event: use C99 initializers for mem_event_request_t users Use C99 initializers for mem_event_request_t users to make sure req is always cleared, even with local debug patches that shuffle code around to have a single exit point. The common case is to use and send req, so it does n...

The following two patches are about how to speed up in xenpaging when page in pages. On suse11-64 with 4G memory,if we page out 2G pages,it will cost about 15.5 seconds, but take 2088 seconds to finish paging in.If page-in costs too much time,it will cause unmesurable problems when vm or dom0 access the paged_out page,such as BSOD,crash. What鈥檚 more,the dom0 is always in high I/O pressure.

...xen/arch/x86/efi/runtime.c | 2 +- xen/arch/x86/hvm/hvm.c | 26 +++++++------- xen/arch/x86/microcode.c | 2 +- xen/arch/x86/mm.c | 24 +++++++------- xen/arch/x86/mm/hap/hap.c | 2 +- xen/arch/x86/mm/mem_event.c | 2 +- xen/arch/x86/mm/paging.c | 2 +- xen/arch/x86/mm/shadow/common.c | 2 +- xen/arch/x86/physdev.c | 2 +- xen/arch/x86/platform_hypercall.c | 2 +- xen/arch/x86/sysctl.c | 2 +- xen/arch/x...

hi, How can I get corresponding shadowed page number of a virtual address in vm? -- Best Regards, Mohamad Rezaei

-- Advanced Micro Devices GmbH Sitz: Dornach, Gemeinde Aschheim, Landkreis München Registergericht München, HRB Nr. 43632 WEEE-Reg-Nr: DE 12919551 Geschäftsführer: Alberto Bozzo, Andrew Bowd _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...c | 7 +++++++ xen/include/asm-x86/hvm/hvm.h | 1 + 3 files changed, 15 insertions(+), 0 deletions(-) diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c index df021de..47eb18d 100644 --- a/xen/arch/x86/hvm/hvm.c +++ b/xen/arch/x86/hvm/hvm.c @@ -68,6 +68,7 @@ #include <public/mem_event.h> bool_t __read_mostly hvm_enabled; +bool_t __read_mostly hypervisor_access_uc_hvm_memory; unsigned int opt_hvm_debug_level __read_mostly; integer_param("hvm_debug", opt_hvm_debug_level); @@ -2483,6 +2484,9 @@ static enum hvm_copy_result __hvm_copy( return HVMCOPY_u...

...ch/x86/efi/runtime.c | 2 +- xen/arch/x86/hvm/hvm.c | 26 +++++++------- xen/arch/x86/microcode.c | 2 +- xen/arch/x86/mm.c | 36 ++++++++++++-------- xen/arch/x86/mm/hap/hap.c | 2 +- xen/arch/x86/mm/mem_event.c | 2 +- xen/arch/x86/mm/paging.c | 2 +- xen/arch/x86/mm/shadow/common.c | 2 +- xen/arch/x86/oprofile/backtrace.c | 4 ++- xen/arch/x86/oprofile/xenoprof.c | 6 ++-- xen/arch/x86/physdev.c | 2 +- xen/arc...