From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: pvops dom0
Date: Wed, 13 Nov 2013 18:31:38 +0000 [thread overview]
Message-ID: <5283C58A.20006@citrix.com> (raw)
In-Reply-To: <5283C306.9060600@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 603 bytes --]
On 13/11/13 18:20, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Hello, all. I see something strange: apparently it was intended that
> dom0 kernels would have feature "dom0". But vmlinu[xz] even with dom0
> doesn't have such feature set. Does that mean that xen has a bug in not
> checking it and vmlinu[xz] has a bug in not having this feature?
There is (almost) no code difference between a PVops dom0 and domU, and
certainly nothing now that requires recompiling.
dom0/domU is really just a permissions distinction. dom0 is permitted
full control of all hardware and all other domUs.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 947 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-13 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 18:20 pvops dom0 Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-13 18:31 ` Andrew Cooper [this message]
2013-11-13 18:34 ` Konrad Rzeszutek Wilk
2013-11-15 7:53 ` Jan Beulich
2013-11-15 10:57 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-11-15 10:59 ` 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=5283C58A.20006@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=phcoder@gmail.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 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).