[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] problem using xenbus interface
On 8/8/05, Dan Smith <danms@xxxxxxxxxx> wrote: > > > err = xenbus_scanf("/", "restart_mode", "%s", mode); > > This will try to read //restart_mode, not /domain/<DOM>/restart_mode, > which I assume is not what you want. > > Also, there is no way to access keys in the /domain/<DOM> directly, > only keys in subfolders. For example, you should be using something > like /domain/<DOM>/control/restart_mode, like this: > > err = xenbus_scanf("control", "restart_mode", "%s", mode); > > Note the absence of the leading '/' in the directory parameter. This > means the location is relative to the "home directory" of the domain. > > > err = xenbus_mkdir("/", "test"); > > As I understand it, the plan is to remove the xenbus_mkdir() kernel > interface. Directories should be created by the tools. You should > have Xend (or something else) do the creation before the kernel needs > it. I have another idea on this: if directories must be created by tools, we (or somebody desires) will have to patch Xend (or whatever) everytime we have a new kernel module. Imagine that we have 100 third party drivers in the future, are we willing to patch Xend 100 times? Let domU create xenstore nodes itself is a good thing: new kernel drivers can be self-contained. I hope we will not remove xenbus_mkdir(), or if we do, replace it with another equally. regards, aq _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |