This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


RE: [Xen-devel] [Patch 1/2] Re-org dom0_ops.h to allow arch specificdefi

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [Patch 1/2] Re-org dom0_ops.h to allow arch specificdefinition
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 17 Jun 2005 09:25:18 +0100
Delivery-date: Fri, 17 Jun 2005 08:24:22 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVyXEnsibufuu7JRVC9zWVOoEIwJwAuN9GQ
Thread-topic: [Xen-devel] [Patch 1/2] Re-org dom0_ops.h to allow arch specificdefinition
> I'm not sure whether this is right way to go, but sometimes 
> specific architecture may have its own different dom0 
> operations. Attached patch tries to arrange definition of 
> operations to the way where each architecture is allocated 
> with exclusive 64 operation IDs. And common operations occupy 
> first segment.

It probably makes sense not to re-use arch-specific dom0_op numbers
(though there wouldn't be any real abiguity), but I'm not sure its worth
trying to carve up the number space like this.

I guess there's an argument for renaming the arch-specific dom0 ops to
put X86 or IA64 in the name, but I don't think there's any real
confusion. Perhaps we should split out arch definitions from dom0_ops.h?

I'm inclined not to do much in the way of rearranging until post 3.0.
After 3.0 I'd like to rename dom0_ops altogether, and implement finer
grained delegation of control operations. 



Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>