Displaying 3 results from an estimated 3 matches for "guest_from_compat_handl".
Did you mean:
guest_from_compat_handle
2007 Oct 23
6
[PATCH][cpufreq] Xen support for the ondemand governor [1/2] (hypervisor code)
..._t i, nr_cpus;
uint64_t idletime;
+ uint64_t totaltime;
struct vcpu *v;
XEN_GUEST_HANDLE(uint64_t) idletimes;
+ XEN_GUEST_HANDLE(uint64_t) totaltimes;
ret = -ENOSYS;
if ( cpufreq_controller != FREQCTL_dom0_kernel )
break;
guest_from_compat_handle(idletimes, op->u.getidletime.idletime);
+ guest_from_compat_handle(totaltimes, op->u.getidletime.totaltime);
nr_cpus = min_t(uint32_t, op->u.getidletime.max_cpus, NR_CPUS);
for ( i = 0; i < nr_cpus; i++ )
@@ -312,11 +315,16 @@ ret_t do_platform_op(XEN_GUEST_H...
2012 Aug 16
27
[PATCH v3 0/6] ARM hypercall ABI: 64 bit ready
Hi all,
this patch series makes the necessary changes to make sure that the
current ARM hypercall ABI can be used as-is on 64 bit ARM platforms:
- it defines xen_ulong_t as uint64_t on ARM;
- it introduces a new macro to handle guest pointers, called
XEN_GUEST_HANDLE_PARAM (that has size 4 bytes on aarch and is going to
have size 8 bytes on aarch64);
- it replaces all the occurrences of
2011 Aug 15
36
expose MWAIT to dom0
There''re basically two methods to enter a given C-state: legacy (hlt + I/O read),
and native(using mwait). MWAIT is always preferred when both underlying CPU
and OS support, which is a more efficient way to conduct C-state transition.
Xen PM relies on Dom0 to parse ACPI Cx/Px information, which involves one
step to notify BIOS about a set of capabilities supported by OSPM. One capability