From: Mark Williamson <mark.williamson@cl.cam.ac.uk>
To: xen-devel@lists.xensource.com
Cc: David Stone <unclestoner@gmail.com>, Daniel Stodden <stodden@cs.tum.edu>
Subject: Re: Are drivers in Dom0 virtualized in any way
Date: Sun, 2 Dec 2007 05:35:07 +0000 [thread overview]
Message-ID: <200712020535.08959.mark.williamson@cl.cam.ac.uk> (raw)
In-Reply-To: <1193936138.32421.6.camel@thinkpad.localdomain>
> > That helped a lot, I understand much better now. Just to be 100%
> > certain though, the net result of the details you provided are that
> > the physical drivers (not the back drivers) running in Dom0 have not
> > been modified from their source as it is in the vanilla linux kernel?
The only difference is that functions called by those drivers (or macros used
by them) may have xen-specific implementations. However, the API used for
the drivers themselves has not changed and the drivers generally need no
changes.
Conversely, the backend drivers are aware of Xen-related issues but they just
plumb into the block / net stack at a fairly generic layer and are unaware of
the nature of the underlying device - Linux handles that.
Cheers,
Mark
--
Dave: Just a question. What use is a unicyle with no seat? And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!
next prev parent reply other threads:[~2007-12-02 5:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 13:47 Are drivers in Dom0 virtualized in any way David Stone
2007-11-01 15:04 ` Daniel Stodden
2007-11-01 16:41 ` David Stone
2007-11-01 16:55 ` Daniel Stodden
2007-12-02 5:35 ` Mark Williamson [this message]
2007-12-03 9:24 ` dom0 is HVM or PV, in the HVM intel-vt? tgh
2007-12-03 9:32 ` Han, Weidong
2007-12-03 17:01 ` Mark Williamson
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=200712020535.08959.mark.williamson@cl.cam.ac.uk \
--to=mark.williamson@cl.cam.ac.uk \
--cc=stodden@cs.tum.edu \
--cc=unclestoner@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.