similar to: Credit Scheduler code question

Displaying 20 results from an estimated 300 matches similar to: "Credit Scheduler code question"

2012 Nov 16
3
How to activate all VPCUS for a domU?
Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are
2012 Nov 16
3
How to activate all VPCUS for a domU?
Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are
2012 Oct 10
7
[PATCH 0 of 7] Miscellaneous updates
Clearing out my local queue of changes before applying other''s.
2010 Aug 09
2
[PATCH 0 of 2] Scheduler: Implement yield for credit scheduler
As discussed in a previous e-mail, this patch series implements yield for the credit scheduler. This allows a VM to actually yield (give up the cpu to another VM) when it wants to. This has been shown to be effective when used in the spinlock code to avoid wasting time spinning when another vcpu is not currently scheduled. _______________________________________________ Xen-devel mailing list
2013 Jun 04
13
[PATCH] x86/vtsc: update vcpu_time after hvm_set_guest_time
When using a vtsc, hvm_set_guest_time changes hvm_vcpu.stime_offset, which is used in the vcpu time structure to calculate the tsc_timestamp, so after updating stime_offset we need to propagate the change to vcpu_time in order for the guest to get the right time if using the PV clock. This was not done correctly, since in context_switch update_vcpu_system_time was called before vmx_do_resume,
2005 Jul 13
14
[Patch] Fix IDLE issue with sedf scheduler on IA64
Hi, Dan, This patch fixes strange behavior on IA64, that IDLE is scheduled more than Dom0 with default sEDF scheduler. The key point is reprogram_ac_timer at the end of ac_timer dispatcher, which programs local apic timer with expire of next ac_timer on x86. Higher precision lapic timer can trigger ac_timer more precisely than simply done in PIT interrupt handler. That works perfectly on x86
2009 Mar 26
1
AW: VCPU amount
Hi, I don''t want to hijack this thread. But as I lately posted a question which mainly was about weight and cap and this fits in perfectly (and also you seem to be an expert here), I repeat it below. In the meantime I saw an academic article Ludmilla Cherkasova et al. from which I understood that you have to careful that a Dom0 doesn''t get too much weight, as otherwise
2005 Feb 23
19
Calculating real cpu usage of Xen domains correctly!
Hi all, With the new vm-tools we are trying to get top like capabilities going correctly. Currently we have a program vm-list that has some of this capability but is dependent on the cpu time given by libxc calls (xc_get_dom_info & xc_domain_get_cpu_usage). These two functions give you how much time (in nanoseconds, why is this not documented) the domain has been actively used. Approaches:
2005 May 17
8
scheduler independent forced vcpu selection
I''m working on a new hypercall, do_confer, which allows the directed yielding of a vcpu to another vcpu. It is mainly used when a vcpu fails to acquire a spinlock, yielding to the lock holder instead of spinning. I ported the ppc64 spinlock implementation for the i386 linux portion. In implementing the hypercall, I''ve been trying to figure out how to get the scheduler
2008 Jun 16
8
Vcpu allocation for a newly created domU
Hi all, I am having confusion regarding the way a newly created domain is allocated vcpu. Initially during dom0 creation alloc_vcpu is called to create vcpu structs for all the available cpu''s and assigned to dom0. But its not the case for domU creation. 1. So how will dom0 relinquish/share vcpu to/with a newly created domU. Does this happen as part of the shared_info page mapping??
2013 Mar 08
2
[PATCH v2 1/2] credit2: Fix erronous ASSERT
In order to avoid high-frequency cpu migration, vcpus may in fact be scheduled slightly out-of-order. Account for this situation properly. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> credit2: Fix erronous ASSERT In order to avoid high-frequency cpu migration, vcpus may in fact be scheduled slightly out-of-order. Account for this situation properly. v2: - Update comment
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
2011 Mar 17
0
Squeeze / Xen 4.01 : xm vcpu-set
Hi, I don''t understand something about the vcpu-set function. My configuration: *memory = 2048 cpu = ''1-2'' maxvcpu = 4 vcpus = 1* When the DomU is running, and when i try to set 2 or 3 vpcu i get the error : xm vcpu-set domain_name 2 *Error: Cannot set vcpus greater than max vcpus on running domain Usage: xm vcpu-set <Domain> <vCPUs> Set the number of
2013 Nov 14
33
VCPUOP_set_periodic_timer
Hi all, I need a periodic timer running at ideally at 125 microseconds and at least 500 microseconds. I''ve just found the VCPUOP_set_periodic_timer, however there is a comment saying "periods less than one millisecond may not be supported". I will be running on an x64 machine. Is this supported? If not, is there any alternate means of generating a fast interrupt? Regards.
2006 Sep 19
3
RE: How to configure VBD hard disk drives in Linux HVMdomain?
>-----Original Message----- >From: xen-users-bounces@lists.xensource.com >[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang >Sent: 2006年9月19日 8:36 >To: xen-users@lists.xensource.com >Subject: [Xen-users] How to configure VBD hard disk drives in Linux >HVMdomain? >how to do it in the config file? Your config is partly right. But it also needs a Qemu
2012 Jun 24
11
Xen 10GBit Ethernet network performance (was: Re: Experience with Xen & AMD Opteron 4200 series?)
Hey, On Mon, Feb 27, 2012 at 10:26 PM, Linus van Geuns <linus@vangeuns.name> wrote: > Hey, > > I am currently considering a two machine Xen setup based on AMD Opterons, > more precisely Dell R515s or R415s with dual Opteron 4274HE. > Does anyone has some Xen setup(s) running on top of Opterons 4274HE, Opteron > 4200 or Dell R515 machines and is willing to share some
2010 May 07
0
[PATCH] More xenalyze type fixes
Looks like you added some more type problems which break the 64-bit build. Signed-of-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r 668cf7d7cc8c xenalyze.c --- a/xenalyze.c Thu May 06 16:27:50 2010 -0500 +++ b/xenalyze.c Fri May 07 16:22:10 2010 -0700 @@ -4382,8 +4382,8 @@ if ( opt.dump_all ) printf(" %s npf gpa %llx q %x mfn %llx t %d\n",
2007 Jun 09
3
vcpu performance : 1 vcpu for all guets or 4 vpcu ?
Hello all ;) Tell I have a Xeon server with 4 vcpus If on this box I have some guets, tell 10, what is the best solutions : - Set all guests to 1 vcpu ? - Set all guests to 4 vcpus ? I well understand that if I set a guest with 4 vcpus and all others only with one vpcus, then the one with 4 vcpus will have more "cpu time" available than others guests. But in case I''d like
2013 May 01
8
[PATCH 0/2] runstate_memory_area on ARM
Hi all, this patch series introduces support for runstate_memory_area on ARM. The first patch moves VCPUOP_register_runstate_memory_area to common code, while the second one add VCPUOP_register_runstate_memory_area to the whilelist of vcpu_op hypercalls supported on ARM and properly updates the runstate_memory_area during vcpu context switch. Stefano Stabellini (2): xen: move
2006 Jul 17
0
Critical Information Regarding Your Credit Card
A non-text attachment was scrubbed... Name: not available Type: text/html <html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml"> Size: 12943 bytes Desc: not available Url : http://wrath.rubyonrails.org/pipermail/rails/attachments/20060717/8c639edc/attachment.ksh