From: David Vrabel <david.vrabel@citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>, <linux-kernel@vger.kernel.org>
Cc: <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH 1/2] xen: wrap xenbus on xenfs with COMPAT option
Date: Tue, 1 Dec 2015 13:54:19 +0000 [thread overview]
Message-ID: <565DA68B.9000800@citrix.com> (raw)
In-Reply-To: <565DA473.9030000@cardoe.com>
On 01/12/15 13:45, Doug Goldstein wrote:
> On 12/1/15 4:44 AM, David Vrabel wrote:
>> On 01/12/15 10:42, David Vrabel wrote:
>>> On 30/11/15 21:35, Doug Goldstein wrote:
>>>> Since Xen 4.6.0, using xenbus via xenfs (/proc/xen/xenbus) is deprecated
>>>> and /dev/xen/xenbus via pvops is used instead. This is an effort to
>>>> eventually drop this interface after a reasonable amount of time.
>>>
>>> I would prefer the ... /proc/xen/evtchn files to be
>>
>> I meant /proc/xen/privcmd here.
>>
>> David
>>
>
> I can look into that. I do have a few questions, some of which are out
> of scope from the original patch.
>
> Would it be preferable to just remove "xenbus" from the xenfs
> filesystem? Ever since Linux 3.14 even if you are running a version of
> Xen earlier than 4.6 you will not be able to have a disaggregated
> xenstore (which is the xenbus consumer) due to the addition of F_ATOMIC_POS.
If /proc/xen/xenbus is made a symlink then older Xen toolstacks will
work again.
> Is it safe for a kernel virtual filesystem to provide a symlink outside
> of itself where the destination can't be verified?
Yes. The symlink target is just a string containing a path.
> Since the /proc/xen mount point has been marked as COMPAT for nearly 6
> years would the eventual goal be to move xenfs to somewhere like
> /sys/hypervisor given that most of the virtual filesystems are mounted
> under /sys now days?
No. The information might move to /sys/hypervisor (or elsewhere) but
xenfs will always be mounted in /proc/xen (or not mounted at all).
David
prev parent reply other threads:[~2015-12-01 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 21:35 [PATCH 1/2] xen: wrap xenbus on xenfs with COMPAT option Doug Goldstein
2015-11-30 21:35 ` [PATCH 2/2] xen: wrap privcmd " Doug Goldstein
2015-12-01 10:42 ` [Xen-devel] [PATCH 1/2] xen: wrap xenbus " David Vrabel
2015-12-01 10:44 ` David Vrabel
2015-12-01 13:45 ` Doug Goldstein
2015-12-01 13:54 ` David Vrabel [this message]
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=565DA68B.9000800@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=cardoe@cardoe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).