From: David Hildenbrand <david@redhat.com>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Leonardo Bras Soares Passos <lsoaresp@redhat.com>
Subject: Re: [PATCH 1/3] hostmem: Detect and cache fs type for file hostmem
Date: Wed, 19 Apr 2023 09:28:21 +0200 [thread overview]
Message-ID: <cdec800a-80ab-18f7-2667-9bc7a8917f09@redhat.com> (raw)
In-Reply-To: <20230418225749.1049185-2-peterx@redhat.com>
On 19.04.23 00:57, Peter Xu wrote:
> Detect the file system for a memory-backend-file object and cache it within
> the object if possible when CONFIG_LINUX (using statfs).
>
> Only support the two important types of memory (tmpfs, hugetlbfs) and keep
> the rest as "unknown" for now.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> backends/hostmem-file.c | 37 ++++++++++++++++++++++++++++++++++++-
> include/sysemu/hostmem.h | 1 +
> 2 files changed, 37 insertions(+), 1 deletion(-)
>
> diff --git a/backends/hostmem-file.c b/backends/hostmem-file.c
> index 25141283c4..2484e45a11 100644
> --- a/backends/hostmem-file.c
> +++ b/backends/hostmem-file.c
> @@ -18,13 +18,17 @@
> #include "sysemu/hostmem.h"
> #include "qom/object_interfaces.h"
> #include "qom/object.h"
> +#ifdef CONFIG_LINUX
> +#include <sys/vfs.h>
> +#include <linux/magic.h>
> +#endif
>
> OBJECT_DECLARE_SIMPLE_TYPE(HostMemoryBackendFile, MEMORY_BACKEND_FILE)
>
>
> struct HostMemoryBackendFile {
> HostMemoryBackend parent_obj;
> -
> + __fsword_t fs_type;
> char *mem_path;
> uint64_t align;
> bool discard_data;
> @@ -52,6 +56,15 @@ file_backend_memory_alloc(HostMemoryBackend *backend, Error **errp)
> return;
> }
>
> +#ifdef CONFIG_LINUX
> + struct statfs fs;
> + if (!statfs(fb->mem_path, &fs)) {
> + fb->fs_type = fs.f_type;
> + } else {
> + fb->fs_type = 0;
> + }
> +#endif
> +
Instead of using statfs, why not implement something like
qemu_fd_getpagesize(), that also relies on HUGETLBFS_MAGIC already, meaning
size_t qemu_fd_type(int fd)
which uses fstatfs() instead? As an abstraction, as Daniel suggests, use
a new enum to return the type -- "0" meaning "unknown".
Then you can even avoid the caching in hostmem code and simply call it
directly from uffd code.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-04-19 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 22:57 [PATCH 0/3] migration/hostmem: Allow to fail early for postcopy on specific fs type Peter Xu
2023-04-18 22:57 ` [PATCH 1/3] hostmem: Detect and cache fs type for file hostmem Peter Xu
2023-04-19 7:01 ` Daniel P. Berrangé
2023-04-19 7:28 ` David Hildenbrand [this message]
2023-04-19 14:46 ` Peter Xu
2023-04-18 22:57 ` [PATCH 2/3] vl.c: Create late backends before migration object Peter Xu
2023-04-18 22:57 ` [PATCH 3/3] migration/postcopy: Detect file system on dest host Peter Xu
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=cdec800a-80ab-18f7-2667-9bc7a8917f09@redhat.com \
--to=david@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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).