From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org, Yeqi Fu <fufuyqqqqqq@gmail.com>
Cc: "Laurent Vivier" <laurent@vivier.eu>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [RFC PATCH 0/2] linux-user: extend -dfilter to accept paths
Date: Fri, 11 Aug 2023 17:28:28 +0100 [thread overview]
Message-ID: <20230811162830.2278032-1-alex.bennee@linaro.org> (raw)
I was getting lost on debugging output and I couldn't get the mapped
address of libnative to be stable. So to help I hacked up this
extension which may or may not be worth developing further.
Consider this a debugging RFC tool for now.
Alex Bennée (2):
linux-user: implement some basic FD<->path tracking
linux-user: implement name lookup for dfilter
include/qemu/log.h | 12 ++++++
linux-user/syscall.c | 90 +++++++++++++++++++++++++++++++++++++++++---
util/log.c | 36 +++++++++++++++++-
3 files changed, 131 insertions(+), 7 deletions(-)
--
2.39.2
next reply other threads:[~2023-08-11 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 16:28 Alex Bennée [this message]
2023-08-11 16:28 ` [RFC PATCH 1/2] linux-user: implement some basic FD<->path tracking Alex Bennée
2023-08-11 16:28 ` [RFC PATCH 2/2] linux-user: implement name lookup for dfilter Alex Bennée
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=20230811162830.2278032-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=fufuyqqqqqq@gmail.com \
--cc=laurent@vivier.eu \
--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 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).