search for: mem_access

Check the return values of the libxc mem_access calls. Free allocated structures (platform_info, domain_info) on errors during initialization and exit. Unbind VIRQ, close event channel and connection to Xen on errors during initialization Signed-off-by: Aravindh Puthiyaparambil <aravindh@virtuata.com> Acked-by: Ian Jackson <ian.jackson...

I have a 12GB 64-bit Linux HVM guest (CentOS 5.5). When I look at the e820 map in the guest, I see the following: BIOS-provided physical RAM map: BIOS-e820: 0000000000010000 - 000000000009e000 (usable) BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000f0000000 (usable) BIOS-e820:

...ng, 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 | 21 ++- tools/libxc/xc_mem_event.c | 15 -- tools/libxc/xc_mem_paging.c | 33 +++- tools/libxc/xc_memshr.c | 16 +- tools/libxc/xenctrl.h...

Hey We have a static analyzer setup for Xen called Coverity. It allows the code to be inspected for bugs and such. Originally I setup this so that we could make sure that there are no bugs that cause security issues - and as such invited only folks on the security Xen mailing list. But there are other folks who I am sure would like to contribute and as Coverity is pretty amazing at analyzing

...trace: Change trace_var argument to void*, to match __trace_var Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> changeset: 22876:93212e5c88f6 user: Keir Fraser <keir@xen.org> date: Sun Feb 06 17:21:17 2011 +0000 hvm_op: Clean up new mem_access and inject_trap ops. Firstly, they are only for use from privileged entities, so mark them as usable only by code defining __XEN_TOOLS__. Secondly, the check for must-not-operate-on-myself can be done more cleanly. Signed-off-by: Keir Fraser <keir@xen.org>...