All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Pankaj Parakh <me.pankajparakh@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: How to Stop scheduler
Date: Tue, 3 Nov 2009 19:11:20 +0000	[thread overview]
Message-ID: <4AF08058.8070801@eu.citrix.com> (raw)
In-Reply-To: <27a8ee1b0911031102n39adcfc4wd994bc171c41d518@mail.gmail.com>

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@eu.citrix.com> 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@gmail.com> 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
>>>
>>>       
>
>
>
>   

  reply	other threads:[~2009-11-03 19:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 21:02 How to Stop scheduler Pankaj Parakh
2009-11-03 11:48 ` George Dunlap
2009-11-03 11:58   ` George Dunlap
2009-11-03 19:02   ` Pankaj Parakh
2009-11-03 19:11     ` George Dunlap [this message]
2009-11-04  5:38       ` Pankaj Parakh
2009-11-04  5:59         ` Pankaj Parakh
2009-11-04 11:39           ` George Dunlap
2009-11-05  0:43             ` Pankaj Parakh
2009-11-05  9:55               ` George Dunlap
2009-11-05 10:27                 ` George Dunlap
2009-11-05 18:06                   ` Pankaj Parakh
2009-11-10  6:48                 ` Pankaj Parakh
2009-11-10  7:05                   ` Pankaj Parakh
     [not found]                     ` <27a8ee1b0911110337k34a03b7di7b7f71ab2e36ffa1@mail.gmail.com>
2009-11-11 11:38                       ` Fwd: " Pankaj Parakh
2009-11-11 11:48                       ` George Dunlap
2009-11-04  6:02         ` James (song wei)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AF08058.8070801@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=me.pankajparakh@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.