All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Zytaruk, Kelly" <Kelly.Zytaruk@amd.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Question regarding Xen scheduler
Date: Wed, 8 Oct 2014 14:57:02 +0100	[thread overview]
Message-ID: <543542AE.9060607@citrix.com> (raw)
In-Reply-To: <B756807489D6244883AC0B799A6EEC15026B82C8@storexdag02.amd.com>

On 08/10/14 14:05, Zytaruk, Kelly wrote:
> I would like to ask a question as to how the Xen scheduler handles certain situations.  
> From everything that I have read I understand that the scheduler treats Dom0 just like any other DomU in regards to scheduling.

Correct.  (XenServer has a tweak which allows dom0's credit to scale
relative to current system load, but nothing more complicated.)

>
> My question is in regards to interrupt handlers, critical sections and kernel code.  Is the Xen scheduler aware of whether the Dom0 is executing in kernel code versus user mode code?  Can Dom0 kernel mode code be interrupted by the Xen scheduler and then a DomU run for a while before returning back to Dom0 kernel mode code?

All domains may be interrupted by Xen.  Xen itself knows whether the
domain is in kernel or user mode, but the scheduler does not. 

>
> What about interrupt handling routines either in Dom0 or DomU.  Can a Task switch to another DomU / Dom0 occur if in the middle of an interrupt handler?

Yes

>
> What if I am doing something time critical or sequence critical that can't be interrupted?  Is there a way to tell the Xen scheduler that "I am in a critical section and can't be interrupted by another Dom" so that Xen won't task switch until I am done?

No.

>
> Other than reading the source code is there a good reference that I can read for Xen internal details and architecture?  

Not which comes to mind.

~Andrew

  reply	other threads:[~2014-10-08 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08 13:05 Question regarding Xen scheduler Zytaruk, Kelly
2014-10-08 13:57 ` Andrew Cooper [this message]
2014-10-08 14:03   ` Razvan Cojocaru
2014-10-08 15:05     ` Zytaruk, Kelly
2014-10-08 14:03   ` Zytaruk, Kelly
2014-10-10  8:12   ` Jan Beulich
2014-10-24 14:55     ` Dario Faggioli
2014-10-24 20:26       ` Zytaruk, Kelly
2014-10-27  9:18         ` Jan Beulich

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=543542AE.9060607@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Kelly.Zytaruk@amd.com \
    --cc=xen-devel@lists.xen.org \
    /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.