From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Laurent Vivier" <laurent@vivier.eu>,
"Dominik 'Disconnect3d' Czarnota" <dominik.b.czarnota@gmail.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Andreas Arnez" <arnez@linux.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH RESEND 1/6] linux-user: Expose do_guest_openat() and do_guest_readlink()
Date: Wed, 24 May 2023 10:35:09 +0100 [thread overview]
Message-ID: <875y8ixeb2.fsf@linaro.org> (raw)
In-Reply-To: <20230510202654.225689-2-iii@linux.ibm.com>
Ilya Leoshkevich <iii@linux.ibm.com> writes:
> These functions will be required by the GDB stub in order to provide
> the guest view of /proc to GDB.
>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-05-24 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 20:26 [PATCH RESEND 0/6] gdbstub: Add support for info proc mappings Ilya Leoshkevich
2023-05-10 20:26 ` [PATCH RESEND 1/6] linux-user: Expose do_guest_openat() and do_guest_readlink() Ilya Leoshkevich
2023-05-24 9:35 ` Alex Bennée [this message]
2023-05-10 20:26 ` [PATCH RESEND 2/6] gdbstub: Expose gdb_get_process() and gdb_get_first_cpu_in_process() Ilya Leoshkevich
2023-05-24 9:37 ` Alex Bennée
2023-05-10 20:26 ` [PATCH RESEND 3/6] gdbstub: Report the actual qemu-user pid Ilya Leoshkevich
2023-05-24 9:41 ` Alex Bennée
2023-05-10 20:26 ` [PATCH RESEND 4/6] gdbstub: Add support for info proc mappings Ilya Leoshkevich
2023-05-10 20:26 ` [PATCH RESEND 5/6] docs: Document security implications of debugging Ilya Leoshkevich
2023-05-24 10:27 ` Alex Bennée
2023-05-24 11:39 ` Dominik Czarnota
2023-05-10 20:26 ` [PATCH RESEND 6/6] tests/tcg: Add a test for info proc mappings Ilya Leoshkevich
2023-05-24 9:01 ` PING: [PATCH RESEND 0/6] gdbstub: Add support " Ilya Leoshkevich
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=875y8ixeb2.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=arnez@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=dominik.b.czarnota@gmail.com \
--cc=iii@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=philmd@linaro.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 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).