Joakim Dahlstedt
2005-Nov-17 16:22 UTC
[Xen-devel] XenBusState move from the linux tree to the xen tree
Hello, I just went through the latest rewrite of the xenbus/front-end/backend driver rewrite. A new enum is introduced called the XenbusState. This enum is defined in the linux-tree under include/asm-xen/xenbus.h As __any__ OS frontend driver may want to access the backend driver sitting on Linux and as that frontend driver needs to know what the states of XenbusState is I think it would make sense to move that enum to the xen public headers instead. Perhaps under io/xs_wire.h ? Does this make sense to those of you that are knowledgeable with xenbus and the backend/frontend drivers? /Joakim Dahlstedt _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Joakim Dahlstedt
2005-Nov-18 13:31 UTC
[Xen-devel] XenBusState move from the linux tree to the xen tree
Hello, I just went through the latest rewrite of the xenbus/front-end/backend driver rewrite. A new enum is introduced called the XenbusState. This enum is defined in the linux-tree under include/asm-xen/xenbus.h As __any__ OS frontend driver may want to access the backend driver sitting on Linux and as that frontend driver needs to know what the states of XenbusState is I think it would make sense to move that enum to the xen public headers instead. Perhaps under io/xs_wire.h ? Does this make sense to those of you that are knowledgeable with xenbus and the backend/frontend drivers? /Joakim Dahlstedt _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Joakim Dahlstedt
2005-Nov-18 13:43 UTC
[Xen-devel] XenBusState move from the linux tree to the xen tree
Hello, I just went through the latest rewrite of the xenbus/front-end/backend driver rewrite. A new enum is introduced called the XenbusState. This enum is defined in the linux-tree under include/asm-xen/xenbus.h As __any__ OS frontend driver may want to access the backend driver sitting on Linux and as that frontend driver needs to know what the states of XenbusState is I think it would make sense to move that enum to the xen public headers instead. Perhaps under io/xs_wire.h ? Does this make sense to those of you that know xenbus and the backend/frontend drivers? /Joakim Dahlstedt _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel