Displaying 20 results from an estimated 20000 matches similar to: "Power aware credit scheduler"
2008 Dec 08
10
[PATCH] Accurate vcpu weighting for credit scheduler
Hi,
This patch intends to accurate vcpu weighting
for CPU intensive job.
The reason of this problem is that
vcpu round-robin queue blocks large weight vcpus
by small weight vcpus.
For example, we assume following case on 2pcpu environment.
(with 4domains (each domain has 2vcpus))
dom1 vcpu0,1 w128 credit 4
dom2 vcpu0,1 w128 credit 4
dom3 vcpu0,1 w256 credit 8
dom4 vcpu0,1 w512 credit 15
2011 Sep 01
4
[PATCH] xen,credit1: Add variable timeslice
Add a xen command-line parameter, sched_credit_tslice_ms,
to set the timeslice of the credit1 scheduler.
Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
diff -r 4a4882df5649 -r 782284c5b1bc xen/common/sched_credit.c
--- a/xen/common/sched_credit.c Wed Aug 31 15:23:49 2011 +0100
+++ b/xen/common/sched_credit.c Thu Sep 01 16:29:50 2011 +0100
@@ -41,15 +41,9 @@
*/
#define
2008 Oct 22
24
Problems with enabling hypervisor C and P-state control
Hi,
Is there any documentation on enabling hypervisor support for both C
and P-state control?
On xen-unstable and linux-2.6.18-xen.hg, if I enable cpuidle=1 on the
xen command line and then run xenpm, I will get output for C-states
(shown below) but it complains that "Xen cpufreq is not enabled!"
cpu id : 0
total C-states : 2
idle time(ms) : 73264
C0
2007 Aug 29
39
[PATCH] 1/2: cpufreq/PowerNow! in Xen: Time and platform changes
Enable cpufreq support in Xen for AMD Operton processors by:
1) Allowing the PowerNow! driver in dom0 to write to the PowerNow!
MSRs.
2) Adding the cpufreq notifier chain to time-xen.c in dom0.
On a frequency change, a platform hypercall is performed to
scale the frequency multiplier in the hypervisor.
3) Adding a platform hypercall to the hypervisor the scale
the frequency multiplier and reset
2007 Oct 23
6
[PATCH][cpufreq] Xen support for the ondemand governor [1/2] (hypervisor code)
Modify the cpufreq ondemand governor so that it can get idle and
total ticks from the Xen hypervisor. Linux and Xen have different
ideas of what an idle tick is, so the Xen values for both have to
be returned in the same platform hypercall.
Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com>
diff -r b4278beaf354 xen/arch/x86/platform_hypercall.c
--- a/xen/arch/x86/platform_hypercall.c
2008 Sep 09
29
[PATCH 1/4] CPU online/offline support in Xen
This patch implements cpu offline feature.
Best Regards
Haitao Shan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2012 Sep 14
1
[PATCH] xenpm: make argument parsing and error handling more consistent
Specifically, what values are or aren''t accepted as CPU identifier, and
how the values get interpreted should be consistent across sub-commands
(intended behavior now: non-negative values are okay, and along with
omitting the argument, specifying "all" will also be accepted).
For error handling, error messages should get consistently issued to
stderr, and the tool should now
2008 Jul 24
3
FW: cpufreq info propagation
it seems getting lost, and thus resend.
Thanks,
Kevin
-----Original Message-----
From: Tian, Kevin
Sent: 2008年7月24日 8:39
To: ''Jan Beulich''
Cc: Liu, Jinsong; Keir Fraser; xen-devel@lists.xensource.com; mark.langsdorf@amd.com
Subject: RE: [Xen-devel] cpufreq info propagation
>From: Jan Beulich
>Sent: 2008年7月23日 18:13
>>
>>startup info is viable. But how
2007 Jan 30
45
[PATCH] Fix softlockup issue after vcpu hotplug
Stamp softlockup thread earlier before do_timer, because the
latter is the one to actually trigger lock warning for
long-time offline. Or else, I obserevd softlockup warning
easily at manual vcpu hot-remove/plug, or when suspend cancel
into old context.
One point here is to cover both stolen and blocked time to
compare with offline threshold. vcpu hotplug falls into ''stolen''
2010 Oct 26
3
[PATCH 0 of 3] credit2 updates
Address some credit2 issues. This patch series, along with the recent
changes to the cpupools interface, should address some of the strange
credit2 instability.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2008 Sep 19
8
[PATCH] x86: add hypercall to query current underlying pCPU''s frequency
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Index: 2008-09-19/xen/arch/x86/platform_hypercall.c
===================================================================
--- 2008-09-19.orig/xen/arch/x86/platform_hypercall.c 2008-09-19 14:12:02.000000000 +0200
+++ 2008-09-19/xen/arch/x86/platform_hypercall.c 2008-09-19 14:12:56.000000000 +0200
@@ -21,7 +21,7 @@
#include <xen/acpi.h>
2008 Jul 23
3
cpufreq info propagation
Now that I finally got around to update our sources, I had a closer look at
those changes, and apart from stylistic issues on the Linux side (part of
which I may have asked for, but the result was somewhat overdone so
the code is hardly legible now - I''ve got a patch queued to streamline this
a little) I find it rather odd (fragile) that the who-is-in-charge information
gets propagated
2007 Oct 23
2
[PATCH][cpufreq] Xen support for the ondemand governor [2/2] (linux)
Modify the cpufreq ondemand governor so that it can get idle and
total ticks from the Xen hypervisor. Linux and Xen have different
ideas of what an idle tick is, so the Xen values for both have to
be returned in the same platform hypercall. Otherwise, use
basically the same scheme as native Linux.
Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com>
iff -r 9bf1ddd0f6bf
2016 Jan 17
1
CPU Freq Scaling
Hi list,
I'm using C7 and noticed that cpu freq is enabled with governor
conservative. I've used cpupower utils for governor change, but at the
next boot it restart with conservative governor.
I've tried also to start cpupower service and setting OPT in
/etc/sysconfig/cpupower but it does not works.
Can someone point me in the right direction?
Thanks in advance
2006 Dec 18
4
VCPU affinity
What is the best way to pin VCPUs. It looks like the implementation of affinity currently is at best only "soft".
Regards,
K. Y
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2007 Jun 27
10
[PATCH 6/10] Allow vcpu to pause self
Add self pause ability, which is required by vcpu0/dom0 when
running on a AP. This can''t be satisfied by existing interface,
since the new flag also serves as a sync point.
Signed-off-by Kevin Tian <kevin.tian@intel.com>
diff -r d5315422dbc8 xen/common/domain.c
--- a/xen/common/domain.c Mon May 14 18:35:31 2007 -0400
+++ b/xen/common/domain.c Mon May 14 20:21:04 2007 -0400
@@
2008 Jul 01
25
Guest TSC and Xen (Intel and AMD feedback please)
Various versions of Linux under various circumstances select
TSC as the primary clocksource for the kernel. This is
especially true for uniprocessor kernels, but also in some
cases for multiprocessor kernels. In most cases, this
is because a processor bit (tsc_invariant? constant_tsc?)
is passed through directly from the hardware via Xen and
tested by the hvm guest and the result implies that
2012 Nov 15
6
Xen credit scheduler question
Hi all (and Mr. Dunlap in particular),
I have a question about the credit (and ultimately credit2) scheduler that I hope you can help me with.
I have read the white paper "Scheduler development update" and as much material on the credit scheduler as I can find, but I am still not completely clear on how I should think about the cap.
Example scenario:
Server hardware: 2
2007 Apr 18
2
Stolen and degraded time and schedulers
The current Linux scheduler makes one big assumption: that 1ms of CPU
time is the same as any other 1ms of CPU time, and that therefore a
process makes the same amount of progress regardless of which particular
ms of time it gets.
This assumption is wrong now, and will become more wrong as
virtualization gets more widely used.
It's wrong now, because it fails to take into account of several
2007 Apr 18
2
Stolen and degraded time and schedulers
The current Linux scheduler makes one big assumption: that 1ms of CPU
time is the same as any other 1ms of CPU time, and that therefore a
process makes the same amount of progress regardless of which particular
ms of time it gets.
This assumption is wrong now, and will become more wrong as
virtualization gets more widely used.
It's wrong now, because it fails to take into account of several