All of lore.kernel.org
 help / color / mirror / Atom feed
From: hanji unit <hanjiunit@gmail.com>
To: win-pv-devel@lists.xenproject.org, xen-devel@lists.xen.org
Subject: Fwd: XenBus_AddWatch
Date: Fri, 2 Jan 2015 10:10:28 -0500	[thread overview]
Message-ID: <CA+J4q6c+KmAggPpJM8QAGOL6gTM5AM5AHH=J71OOLNQo1e1cew@mail.gmail.com> (raw)
In-Reply-To: <CA+J4q6damheMoEXQq4YmvPY8cidMADwhrrVbcb+MkQ9OKsaucA@mail.gmail.com>

Hello, I am calling XenBus_AddWatch API from a DomU guest in the
win-pvdrivers xenpci driver, and noticed that I am not able to watch
xenstore entries that are outside of the DomU's xenstore tree. For
example, the following call in
XenPci_EvtDeviceD0EntryPostInterruptsEnabled fails with response="EIO"
even if the xenstore permissions for Container and Container/DomU in
xenstore are both "b0":

response = XenBus_AddWatch(xpdd, XN_BASE_GLOBAL, "Container/DomU",
MyCallback, xpdd);

However, the following call works and it watches a xenstore entry
relative to DomUs xenstore tree:

response = XenBus_AddWatch(xpdd, XBT_NIL, "DomU", MyCallback, xpdd);

Writing to an entry outside the DomUs tree is allowed if permissions are b0:

result = XnWriteString(xpdd, XN_BASE_GLOBAL, "Container/DomU", buffer);

It seems like DomUs should be allowed to watch xenstore entries
outside their trees. Is this a bug or is it by design?

Thanks.

       reply	other threads:[~2015-01-02 15:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+J4q6damheMoEXQq4YmvPY8cidMADwhrrVbcb+MkQ9OKsaucA@mail.gmail.com>
2015-01-02 15:10 ` hanji unit [this message]
2015-01-06 10:34 ` [win-pv-devel] XenBus_AddWatch Paul Durrant
     [not found] ` <9AAE0902D5BC7E449B7C8E4E778ABCD0257AF4EF@AMSPEX01CL01.citrite.net>
2015-01-07 22:06   ` hanji unit

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='CA+J4q6c+KmAggPpJM8QAGOL6gTM5AM5AHH=J71OOLNQo1e1cew@mail.gmail.com' \
    --to=hanjiunit@gmail.com \
    --cc=win-pv-devel@lists.xenproject.org \
    --cc=xen-devel@lists.xen.org \
    /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.