From: Julien Grall <julien@xen.org>
To: Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org
Cc: paul@xen.org, Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>, Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH RFC 2/3] xen/domain: add domain hypfs directories
Date: Wed, 9 Dec 2020 16:37:35 +0000 [thread overview]
Message-ID: <75232058-4626-80cb-6f71-4ce5253f3ef6@xen.org> (raw)
In-Reply-To: <20201209161618.309-3-jgross@suse.com>
Hi Juergen,
On 09/12/2020 16:16, Juergen Gross wrote:
> Add /domain/<domid> directories to hypfs. Those are completely
> dynamic, so the related hypfs access functions need to be implemented.
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> V3:
> - new patch
> ---
> docs/misc/hypfs-paths.pandoc | 10 +++
> xen/common/Makefile | 1 +
> xen/common/hypfs_dom.c | 137 +++++++++++++++++++++++++++++++++++
> 3 files changed, 148 insertions(+)
> create mode 100644 xen/common/hypfs_dom.c
>
> diff --git a/docs/misc/hypfs-paths.pandoc b/docs/misc/hypfs-paths.pandoc
> index e86f7d0dbe..116642e367 100644
> --- a/docs/misc/hypfs-paths.pandoc
> +++ b/docs/misc/hypfs-paths.pandoc
> @@ -34,6 +34,7 @@ not containing any '/' character. The names "." and ".." are reserved
> for file system internal use.
>
> VALUES are strings and can take the following forms (note that this represents
> +>>>>>>> patched
This seems to be a left-over of a merge.
> only the syntax used in this document):
>
> * STRING -- an arbitrary 0-delimited byte string.
> @@ -191,6 +192,15 @@ The scheduling granularity of a cpupool.
> Writing a value is allowed only for cpupools with no cpu assigned and if the
> architecture is supporting different scheduling granularities.
>
[...]
> +
> +static int domain_dir_read(const struct hypfs_entry *entry,
> + XEN_GUEST_HANDLE_PARAM(void) uaddr)
> +{
> + int ret = 0;
> + const struct domain *d;
> +
> + for_each_domain ( d )
This is definitely going to be an issue if you have a lot of domain
running as Xen is not preemptible.
I think the first step is to make sure that HYPFS can scale without
hogging a pCPU for a long time.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2020-12-09 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 16:16 [PATCH RFC 0/3] xen: add hypfs per-domain abi-features Juergen Gross
2020-12-09 16:16 ` [PATCH RFC 1/3] xen/hypfs: add support for bool leafs in dynamic directories Juergen Gross
2021-01-08 15:38 ` Jan Beulich
2020-12-09 16:16 ` [PATCH RFC 2/3] xen/domain: add domain hypfs directories Juergen Gross
2020-12-09 16:37 ` Julien Grall [this message]
2020-12-10 7:54 ` Jürgen Groß
2020-12-10 11:51 ` Julien Grall
2020-12-10 12:46 ` Jürgen Groß
2020-12-09 16:16 ` [PATCH RFC 3/3] xen/domain: add per-domain hypfs directory abi-features Juergen Gross
2020-12-09 16:24 ` [PATCH RFC 0/3] xen: add hypfs per-domain abi-features Julien Grall
2020-12-10 7:49 ` Jürgen Groß
2020-12-10 11:57 ` Julien Grall
2021-01-08 15:44 ` Jan Beulich
2021-01-13 10:47 ` Jürgen Groß
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=75232058-4626-80cb-6f71-4ce5253f3ef6@xen.org \
--to=julien@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=paul@xen.org \
--cc=sstabellini@kernel.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 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.