From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: pvops dom0 Date: Wed, 13 Nov 2013 18:31:38 +0000 Message-ID: <5283C58A.20006@citrix.com> References: <5283C306.9060600@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3121548127149130044==" Return-path: In-Reply-To: <5283C306.9060600@gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: =?UTF-8?B?VmxhZGltaXIgJ8+GLWNvZGVyL3BoY29kZXInIFNlcmJpbmVua28=?= Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org --===============3121548127149130044== Content-Type: multipart/alternative; boundary="------------030701070401060702020609" --------------030701070401060702020609 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit 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 --------------030701070401060702020609 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 8bit 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

--------------030701070401060702020609-- --===============3121548127149130044== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============3121548127149130044==--