From: Emmanuel Ackaouy <ackaouy@gmail.com>
To: "Agarwal, Lomesh" <lomesh.agarwal@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: question regarding dom0 scheduling
Date: Fri, 6 Jul 2007 22:26:07 +0200 [thread overview]
Message-ID: <301bf561a729e36766b1e2910557fef8@gmail.com> (raw)
In-Reply-To: <A3258B497F1C1441AD36A2E8B45FD628435CB2@scsmsx412.amr.corp.intel.com>
On Jul 6, 2007, at 22:18, Agarwal, Lomesh wrote:
> How does Xen determines dom0 scheduling? Domains get CPU time slices
> based on weight and cap but how does Xen determine the time slice for
> dom0? Does dom0 preempt dom0 ever? If I put an infinite loop in dom0,
> will that halt the system (as domains will never be scheduled)?
dom0 isn't treated any differently than other domains by default.
you can tweak its weight just like any other domain though.
next prev parent reply other threads:[~2007-07-06 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 20:18 question regarding dom0 scheduling Agarwal, Lomesh
2007-07-06 20:26 ` Emmanuel Ackaouy [this message]
2007-07-06 20:49 ` Agarwal, Lomesh
2007-07-06 22:04 ` Kaushik Barde
2007-07-06 23:23 ` Agarwal, Lomesh
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=301bf561a729e36766b1e2910557fef8@gmail.com \
--to=ackaouy@gmail.com \
--cc=lomesh.agarwal@intel.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.