From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
WeiLiu <wl@xen.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
"George Dunlap" <George.Dunlap@eu.citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Ian Jackson" <ian.jackson@eu.citrix.com>,
"Tim Deegan" <tim@xen.org>, "Julien Grall" <julien.grall@arm.com>,
xen-devel@lists.xenproject.org,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [RFC PATCH 0/5] Add hypervisor sysfs-like support
Date: Wed, 11 Sep 2019 15:01:44 +0200 [thread overview]
Message-ID: <19e6dbb5-82c0-4d7e-321b-0255178b8e75@suse.com> (raw)
In-Reply-To: <02c7841c-1b16-97ec-c12d-695bfe0b766f@suse.com>
On 11.09.19 13:54, Jan Beulich wrote:
> On 11.09.2019 13:29, Juergen Gross wrote:
>> On 11.09.19 13:17, Andrew Cooper wrote:
>>> Second, is xenfs really the best name here? It is ambiguous with the
>>> still-essential (even though it really needs to disappear) Linux
>>> filesystem by the name xenfs.
>>
>> Yes, I'm aware of that ambiguity. I'm absolutely in favor of finding a
>> better name.
>>
>> Maybe xensysfs?
>
> Or just xensys (albeit that's likely getting ambiguous)? I'm
> not fully convinced calling this a file system is a good idea.
> Windows' name-value pair store is called registry, for
> example, despite it also resembling a file system to a certain
> degree.
"Registry" doesn't seem correct regarding the potential dynamically
generated entries.
And with the idea to "mount" it in the dom0 kernel's sysfs I think
xensysfs (or xenhypfs?) seems appropriate.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-09-11 13:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 6:19 [Xen-devel] [RFC PATCH 0/5] Add hypervisor sysfs-like support Juergen Gross
2019-09-11 6:19 ` [Xen-devel] [RFC PATCH 1/5] docs: add feature document for Xen " Juergen Gross
2019-09-11 9:28 ` Jan Beulich
2019-09-11 9:29 ` Juergen Gross
2019-09-11 6:19 ` [Xen-devel] [RFC PATCH 2/5] xen: add basic hypervisor filesystem support Juergen Gross
2019-09-11 6:19 ` [Xen-devel] [RFC PATCH 3/5] libs: add libxenfs Juergen Gross
2019-09-11 6:20 ` [Xen-devel] [RFC PATCH 4/5] tools: add xenfs tool Juergen Gross
2019-09-11 9:30 ` Jan Beulich
2019-09-11 9:57 ` Juergen Gross
2019-09-11 10:07 ` Jan Beulich
2019-09-11 11:34 ` Juergen Gross
2019-09-11 11:50 ` Jan Beulich
2019-09-11 12:41 ` Juergen Gross
2019-09-11 6:20 ` [Xen-devel] [RFC PATCH 5/5] xen: add /buildinfo/config entry to hypervisor filesystem Juergen Gross
2019-09-11 9:24 ` [Xen-devel] [RFC PATCH 0/5] Add hypervisor sysfs-like support Jan Beulich
2019-09-11 10:02 ` Juergen Gross
2019-09-11 11:17 ` Andrew Cooper
2019-09-11 11:29 ` Juergen Gross
2019-09-11 11:54 ` Jan Beulich
2019-09-11 13:01 ` Juergen Gross [this message]
2019-09-11 15:01 ` Jan Beulich
2019-09-11 15:06 ` Juergen Gross
2019-09-11 15:20 ` Jan Beulich
2019-09-11 15:26 ` Juergen Gross
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=19e6dbb5-82c0-4d7e-321b-0255178b8e75@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wl@xen.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).