WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] How to Stop scheduler

To: Pankaj Parakh <me.pankajparakh@xxxxxxxxx>
Subject: Re: [Xen-devel] How to Stop scheduler
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Wed, 4 Nov 2009 11:39:14 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 04 Nov 2009 03:39:44 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=janzch54BDzo8P0SQWmjqTyAchZKnzHntqSjYVFFDWU=; b=FRY4sp7yL39+OHPk8v5G9jN32Cok32oeOeHU9eyrf9q/NxePxrtMuPrOrSEZ6Daoff gyIWcZvqkm7RYHhPq4cfOjJ+Er3tMTm6FpOLNfLK0QNrlRGurjNaIe9IfATy6G+c0bnc BHZiKzCqkkPLIE0A+yS8oupOCgr6LJrDN0Zm4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=ClI1zkiiUqTObxAYMCehvtVUu6f8KzlpRDs7pWBSMoG06VHMy4iL1xd32qcGLf6A6e aFzS5G/zdJZuEg7q2cek+lHM+/kskqjteq5FonwHzjOxJR33brvxscIl6h/IRYXZ4vQG 9RxKm6Q3dR8RsCFSYFbhLfm4grech0zE1zlN4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <27a8ee1b0911032159q285332d7p883854502bccc28a@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <27a8ee1b0911021302n37b76a0bw5259c7b594147abd@xxxxxxxxxxxxxx> <de76405a0911030348v2c127fa1j760ed5d8e1d3384@xxxxxxxxxxxxxx> <27a8ee1b0911031102n39adcfc4wd994bc171c41d518@xxxxxxxxxxxxxx> <4AF08058.8070801@xxxxxxxxxxxxx> <27a8ee1b0911032138u4c8d4e00rb574bbff1487241c@xxxxxxxxxxxxxx> <27a8ee1b0911032159q285332d7p883854502bccc28a@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Nov 4, 2009 at 5:59 AM, Pankaj Parakh <me.pankajparakh@xxxxxxxxx> wrote:
> If I take domain_update_lock for  a domain, what will happen to its
> interrupts for IO completions or any other type..??
> And will it be scheduled if I hold that lock..??

Have you looked at the interrupt delivery / IO completion path, or the
scheduler path, to see if those are affected by the
domain_update_lock()?

Xen is a bit of a twisted web; sometimes you just have to follow a web
of logic around to find out what you're looking for; then, once you've
come to a conclusion, test it by writing some code.

For the scheduling question, you might start with looking at vcpu_runnable().

Peace,
 -George

>
> On Wed, Nov 4, 2009 at 11:08 AM, Pankaj Parakh <me.pankajparakh@xxxxxxxxx>
> wrote:
>>
>> So is that means there will be no interrupt loss, and also clock in
>> the paused domain will be in right and expected time.. ??
>>
>> On Wed, Nov 4, 2009 at 12:41 AM, George Dunlap
>> <george.dunlap@xxxxxxxxxxxxx> wrote:
>> > 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
>> >> <George.Dunlap@xxxxxxxxxxxxx> 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
>> >>> <me.pankajparakh@xxxxxxxxx>
>> >>> 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@xxxxxxxxxxxxxxxxxxx
>> >>>> http://lists.xensource.com/xen-devel
>> >>>>
>> >>>>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>>
>> --
>> Pankaj Parakh
>
>
>
> --
> Pankaj Parakh
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel