search for: xenpf_change_freq

....c --- a/xen/arch/x86/platform_hypercall.c Thu Aug 16 13:27:59 2007 +0100 +++ b/xen/arch/x86/platform_hypercall.c Thu Aug 30 12:08:29 2007 -0500 @@ -252,6 +252,13 @@ ret_t do_platform_op(XEN_GUEST_HANDLE(xe ret = acpi_enter_sleep(&op->u.enter_acpi_sleep); break; + case XENPF_change_freq: + { + do_change_freq((struct vcpu_time_info *) op->u.change_freq.info, op->u.change_freq.old, op->u.change_freq.new, op->u.change_freq.cpu_num); + ret = 0; + } + break; + default: ret = -ENOSYS; break; diff -r 256160ff19b7 xen/arch/x86/time...

...freq; /* in kHz */ +}; +typedef struct xenpf_get_cpu_freq xenpf_get_cpu_freq_t; +DEFINE_XEN_GUEST_HANDLE(xenpf_get_cpu_freq_t); + struct xen_platform_op { uint32_t cmd; uint32_t interface_version; /* XENPF_INTERFACE_VERSION */ @@ -327,6 +337,7 @@ struct xen_platform_op { struct xenpf_change_freq change_freq; struct xenpf_getidletime getidletime; struct xenpf_set_processor_pminfo set_pminfo; + struct xenpf_get_cpu_freq get_cpu_freq; uint8_t pad[128]; } u; }; _______________________________________________ Xe...

From: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Hi all, This series adds a new microcode driver for Xen. The Xen hypervisor can deal with all the low-level details of doing a microcode update (Intel vs AMD, doing all the physical CPUs present on the system, current and future, etc), so all the driver has to do is make a hypercall to upload the microcode into Xen. This only

...(cpu_has(&cpu_data[freq->cpu], X86_FEATURE_CONSTANT_TSC)) + return 0; + + if (val == CPUFREQ_PRECHANGE) + return 0; + + /* change the frequency inside the hypervisor */ + oldmask = current->cpus_allowed; + set_cpus_allowed(current, cpumask_of_cpu(freq->cpu)); + schedule(); + op.cmd = XENPF_change_freq; + op.u.change_freq.info = info; + op.u.change_freq.old = freq->old; + op.u.change_freq.new = freq->new; + op.u.change_freq.cpu_num = freq->cpu; + HYPERVISOR_platform_op(&op); + + for_each_online_cpu(cpu) { + get_time_values_from_xen(cpu); + per_cpu(processed_system_time, cpu) = +...

...be idled */ + /* OUT variables: get cpu nums actually be idled */ + uint32_t idle_nums; +}; +DEFINE_GUEST_HANDLE_STRUCT(xenpf_core_parking); + struct xen_platform_op { uint32_t cmd; uint32_t interface_version; /* XENPF_INTERFACE_VERSION */ @@ -312,6 +325,7 @@ struct xen_platform_op { struct xenpf_change_freq change_freq; struct xenpf_getidletime getidletime; struct xenpf_set_processor_pminfo set_pminfo; + struct xenpf_core_parking core_parking; uint8_t pad[128]; } u; }; -- 1.7.1

Hi Ingo, Here''s the chunk of patches to add Xen Dom0 support (it''s probably worth creating a new xen/dom0 topic branch for it). A dom0 Xen domain is basically the same as a normal domU domain, but it has extra privileges to directly access hardware. There are two issues to deal with: - translating to and from the domain''s pseudo-physical addresses and real machine