From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: How to Stop scheduler Date: Tue, 3 Nov 2009 19:11:20 +0000 Message-ID: <4AF08058.8070801@eu.citrix.com> References: <27a8ee1b0911021302n37b76a0bw5259c7b594147abd@mail.gmail.com> <27a8ee1b0911031102n39adcfc4wd994bc171c41d518@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <27a8ee1b0911031102n39adcfc4wd994bc171c41d518@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pankaj Parakh Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org If you call vcpu_pause(), it atomically increments a counter in the vcpu struct. While that counter is non-zero, the vcpu *will not* be scheduled, interrupts or no. Interrupts will be delivered when it's scheduled again. -George Pankaj Parakh wrote: > If I pause a vcpu/domain using those functions, say if a domain's I/O > request over then its interrupt will raise and it can restart its > scheduling rite..?? How this interrupts are/ can be queued so that > when the vcpu is in pause state, it should nat change its state and > when it come back to wait state, those interrupt will not be lost.. > > On Tue, Nov 3, 2009 at 5:18 PM, George Dunlap > wrote: > >> Do you mean that you want to stop one specific vcpu / domain from >> being scheduled? >> >> If so, you're looking for the following functions: >> vcpu_pause(), vcpu_unpause() >> domain_pause(), domain_unpause(). >> >> They're defined in xen/common/domain.c. >> >> -George >> >> >> On Mon, Nov 2, 2009 at 9:02 PM, Pankaj Parakh wrote: >> >>> Hi All, >>> >>> I am working on a project wherein I wanted to stop the scheduling >>> activity in hypervisor through 'generic' part of scheduler, I have lil >>> confusion as to what all things I need to mask/stop for disabling >>> hypervisor to schedule any vcpu untill I want. >>> >>> Issues which I can think are about I/O waits or Zombie VCPUs. But how >>> to tackle them... I dont know.. >>> >>> I wanted to know what all responsibility the generic scheduler holds >>> in hypervisor, >>> >>> Any type of info or pointer can be useful. >>> >>> Thanks >>> Pankaj Parakh >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel >>> >>> > > > >