search for: privcmd_mmap_entry_t

...ser #endif -typedef struct privcmd_hypercall +struct privcmd_hypercall { __u64 op; __u64 arg[5]; -} privcmd_hypercall_t; +}; +typedef struct privcmd_hypercall privcmd_hypercall_t; -typedef struct privcmd_mmap_entry { +struct privcmd_mmap_entry { __u64 va; __u64 mfn; __u64 npages; -} privcmd_mmap_entry_t; +}; +typedef struct privcmd_mmap_entry privcmd_mmap_entry_t; -typedef struct privcmd_mmap { +struct privcmd_mmap { int num; domid_t dom; /* target domain */ privcmd_mmap_entry_t __user *entry; -} privcmd_mmap_t; +}; +typedef struct privcmd_mmap privcmd_mmap_t; -typedef struct privcmd...

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

I am using Xen 3.3 from source. My PV guest boots fine with the normal kernel and initrd options When I boot the guest with PV GRUB I only get: GNU GRUB version 0.97 (65536K lower / 0K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible