From: aq <aquynh@gmail.com>
To: Dan Smith <danms@us.ibm.com>
Cc: NAHieu <nahieu@gmail.com>,
"List: Xen Developers" <xen-devel@lists.xensource.com>
Subject: Re: problem using xenbus interface
Date: Tue, 9 Aug 2005 15:47:28 +0900 [thread overview]
Message-ID: <9cde8bff05080823471ed79f37@mail.gmail.com> (raw)
In-Reply-To: <m3slxktuns.fsf@theine.beaverton.ibm.com>
On 8/8/05, Dan Smith <danms@us.ibm.com> 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
next prev parent reply other threads:[~2005-08-09 6:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 12:26 problem using xenbus interface NAHieu
2005-08-08 13:39 ` Dan Smith
2005-08-09 6:47 ` aq [this message]
2005-08-09 2:21 ` Rusty Russell
2005-08-09 2:53 ` NAHieu
2005-08-09 3:14 ` NAHieu
2005-08-09 3:34 ` NAHieu
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=9cde8bff05080823471ed79f37@mail.gmail.com \
--to=aquynh@gmail.com \
--cc=danms@us.ibm.com \
--cc=nahieu@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.