Displaying 7 results from an estimated 7 matches for "xc_misc".
2012 Jan 17
2
Problems calling HVMOP_flush_tlbs
Hello xen-devel,
I am using xen 4.2.1 and have tried the following with kernel 3.0.0 and
3.2.1.
I am trying to invoke the HVMOP_flush_tlbs hypercall but have been
unsuccessful. I am basing my call on the functions in in xc_misc.c,
trying to guess what is meant by "@arg must be null" in the comment
where HVMOP_flush_tlbs is defined. What is the correct way to invoke
this hypercall?
If I call it like this, I receive an invalid parameter (EINVAL) error:
struct privcmd_hypercall
{
uint64_t op...
2006 Sep 29
4
[PATCH 4/6] xen: export NUMA topology in physinfo hcall
...node2:16-23
node3:24-31
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
diffstat output:
b/xen/include/public/numa_structs.h | 26 ++++++
tools/libxc/xc_misc.c | 4 +
tools/libxc/xenctrl.h | 3
tools/python/xen/lowlevel/xc/xc.c | 77 ++++++++++++++++----
tools/python/xen/xend/XendNode.py | 67 +++++++++++++++++
tools/xenmon/xenbaked.c...
2006 Apr 14
8
[rfc] [patch] 32/64-bit hypercall interface revisited
Last year we had a discussion[1] about how the hypercall ABI
unfortunately contains fields that change width between 32- and 64-bit
builds. This is a huge problem as we come up on the python management
stack for ppc64, since the distributions ship 32-bit python. A 32-bit
python/libxc cannot currently manage a 64-bit hypervisor.
I had a patch but was unable to test it, and some other things were
2005 Jul 04
0
[PATCH 2/2] xm info (2)
...: 1
cores_per_socket : 1
hyperthreads_per_core : 1
cpu_mhz : 1094
memory : 511
free_memory : 122
---
Signed-off-by: Nguyen Anh Quynh <aquynh@gmail.com>
# diffstat xminfo9.patch
libxc/xc.h | 20 +++++++++++++++
libxc/xc_misc.c | 40 +++++++++++++++++++++++++++++++
python/xen/lowlevel/xc/xc.c | 56 +++++++++++++++++++++++++++++++++++++++++++-
python/xen/xend/XendNode.py | 17 ++++++++++---
4 files changed, 128 insertions(+), 5 deletions(-)
_______________________________________________
Xen-devel mai...
2005 Jul 03
11
[PATCH] xm info
...cores_per_socket : 1
hyperthreads_per_core : 1
cpu_mhz : 1094
memory : 511
free_memory : 122
--
Signed-off-by: Nguyen Anh Quynh <aquynh@gmail.com>
# diffstat xminfo8.patch
tools/libxc/xc.h | 20 +++++++++++++
tools/libxc/xc_misc.c | 40 +++++++++++++++++++++++++++
tools/python/xen/lowlevel/xc/xc.c | 55 +++++++++++++++++++++++++++++++++++++-
tools/python/xen/xend/XendNode.py | 16 ++++++++---
xen/arch/x86/dom0_ops.c | 1
xen/common/kernel.c | 46 +++++++++++++++---------------...
2012 Jul 04
53
[PATCH 00 of 10 v3] Automatic NUMA placement for xl
Hello,
Third version of the NUMA placement series Xen 4.2.
All the comments received during v2''s review have been addressed (more details
in single changelogs).
The most notable changes are the following:
- the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the
recent patches that allows us to allocate bitmaps of different sizes;
- the heuristics for deciding
2005 Feb 18
14
autotoolizing xen?
Hi there!
I was wondering what the general opinion on autotoolizing xen is? I am
volunteering to do so, if there is interest in updating the build system to
use autoconf, automake and/or libtool.
Is one configure script for all of xen enough or do you want to be able to
configure all/some tools separately? I know that Anthony is no fan of
libtool... are there more reservations about some