xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Valzcig <gvalzcig@gmail.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: domU to dom0 switch question
Date: Fri, 2 Apr 2010 22:28:59 -0400	[thread overview]
Message-ID: <k2s4f493b121004021928web72f7cs8d290c7c1eab6ddd@mail.gmail.com> (raw)
In-Reply-To: <4BB6A465.1000506@goop.org>


[-- Attachment #1.1: Type: text/plain, Size: 2136 bytes --]

On Fri, Apr 2, 2010 at 10:13 PM, Jeremy Fitzhardinge <jeremy@goop.org>wrote:

> On 04/02/2010 04:02 PM, George Valzcig wrote:
>
>> I have two questions on between a switch one dom to another dom in Xen. I
>> hope this is the right forum to ask these questions ...
>>
>> 1) other than I / O, there is no reason to switch from one domU to dom0
>> (memory page remapping etc)? If I have a 1 CPU in my physical machine and I
>> run a domU with while loop that does nothing but use CPU, there is no reason
>> to switch to dom0?
>> 2) In Xen PV is the hyper call entry page in the address space of the domU
>> - so call to a mapped hyper call not cause context switch - yes?
>>
>
> I don't follow your questions.
>
> "Dom0" is the domain started by Xen automatically at boot time, which is
> privileged and is typically used for its hardware device drivers and
> systemwide administrative functions.  "DomU" is a less privileged "guest"
> domain, which may be either paravirtualized (PV) or using hardware
> virtualization features (HVM).
>
> Note that "dom0" and "domU" are just roles; a single (pvops Linux) kernel
> image can be used unchanged as dom0, PV domU or HVM domU.
>
> You seem to be using the terms "dom0" and "domU" in some other way, so I
> think you need to clarify the question before you get the answer you're
> looking for.
>
>
Thanks for reply. Sorry for unclear question.

I read from the Xen paper dom0 is used for I/O backend driver - you also
explain it - thanks. So if some domU wants to I/O, *and only one physical
CPU*, domU gets unscheduled - dom0 scheduled - yes?

My question 1 is, apart from I/O backend driver, is dom0 used for anything
else? I assume application running on domU no I/O. Any other reason why domU
will require the help of dom0.

My question 2 is, domU requests some service (like page table update) using
hypercall. Will this (executing the hypercall and related code) need dom0?

My questions because, I want to understand the increased number of context
switches and TLB cost (as reported in the paper "The cost of virtualization"
by Ulrich Drepper) in the case of Xen.

Thanks.



>    J
>

[-- Attachment #1.2: Type: text/html, Size: 2943 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

  reply	other threads:[~2010-04-03  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02 23:02 domU to dom0 switch question George Valzcig
2010-04-03  2:13 ` Jeremy Fitzhardinge
2010-04-03  2:28   ` George Valzcig [this message]
2010-04-04 14:11     ` George Valzcig
2010-04-05 16:58     ` Jeremy Fitzhardinge

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=k2s4f493b121004021928web72f7cs8d290c7c1eab6ddd@mail.gmail.com \
    --to=gvalzcig@gmail.com \
    --cc=jeremy@goop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).