From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH] 9pfs: improve v9fs_open() tracing
Date: Mon, 30 Dec 2024 10:50:59 +0100 [thread overview]
Message-ID: <45674069.kNWJ3c3XjC@silver> (raw)
In-Reply-To: <E1tN8RJ-008jNq-5L@kylie.crudebyte.com>
On Monday, December 16, 2024 11:30:09 AM CET Christian Schoenebeck wrote:
> Improve tracing of 9p 'Topen' request type by showing open() flags as
> human-readable text.
>
> E.g. trace output:
>
> v9fs_open tag 0 id 12 fid 2 mode 100352
>
> would become:
>
> v9fs_open tag=0 id=12 fid=2 mode=100352(RDONLY|NONBLOCK|DIRECTORY|
> TMPFILE|NDELAY)
>
> Therefor add a new utility function qemu_open_flags_tostr() that converts
> numeric open() flags from host's native O_* flag constants to a string
> presentation.
>
> 9p2000.L and 9p2000.u protocol variants use different numeric 'mode'
> constants for 'Topen' requests. Instead of writing string conversion code
> for both protocol variants, use the already existing conversion functions
> that convert the mode flags from respective protocol constants to host's
> native open() numeric flag constants and pass that result to the new
> string conversion function qemu_open_flags_tostr().
>
> Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> ---
> hw/9pfs/9p-util-generic.c | 44 +++++++++++++++++++++++++++++++++++++++
> hw/9pfs/9p-util.h | 6 ++++++
> hw/9pfs/9p.c | 9 +++++++-
> hw/9pfs/meson.build | 1 +
> hw/9pfs/trace-events | 2 +-
> 5 files changed, 60 insertions(+), 2 deletions(-)
> create mode 100644 hw/9pfs/9p-util-generic.c
Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
Thanks!
/Christian
next prev parent reply other threads:[~2024-12-30 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 10:30 [PATCH] 9pfs: improve v9fs_open() tracing Christian Schoenebeck
2024-12-16 11:36 ` Christian Schoenebeck
2024-12-30 9:50 ` Christian Schoenebeck [this message]
2025-01-03 11:31 ` Christian Schoenebeck
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=45674069.kNWJ3c3XjC@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.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.