From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: "Laurent Vivier" <laurent@vivier.eu>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"David Hildenbrand" <david@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
qemu-s390x@nongnu.org
Subject: Re: [PATCH v4 0/8] gdbstub: Add support for info proc mappings
Date: Tue, 27 Jun 2023 16:14:01 +0100 [thread overview]
Message-ID: <87h6qtym2j.fsf@linaro.org> (raw)
In-Reply-To: <20230621203627.1808446-1-iii@linux.ibm.com>
Ilya Leoshkevich <iii@linux.ibm.com> writes:
> v3: https://lists.gnu.org/archive/html/qemu-devel/2023-06/msg01311.html
> v3 -> v4: Fix the 32-bit build (Alex).
> Enable the test on all architectures and ignore certain
> expected failures (Alex). I tried this with the latest
> gdb-multiarch and it works. The only skip is on x86_64,
> as expected.
>
> v2: https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg06837.html
> v2 -> v3: Use openat() instead of safe_openat() (new patch: 2/8).
> Add /proc/self/smaps emulation (new patch: 3/8).
> With these 2 changes, the minor issues previously mentioned in
> the patch 6/8 are gone.
>
> v1: https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg02614.html
> v1 -> v2: Reword the 5/6 commit message (Dominik).
> Add R-bs.
> Patches that need review:
> 4/6 gdbstub: Add support for info proc mappings
> 6/6 tests/tcg: Add a test for info proc mappings
>
> Hi,
>
> this series partially implements the Host I/O feature of the GDB Remote
> Serial Protocol in order to make generate-core-file work with qemu-user.
> It borrows heavily from the abandoned patch by Dominik [1], hence 4/6
> carries the respective Co-developed-by: tag. I also peeked at
> gdbserver/hostio.cc quite a few times.
Queued to gdbstub/next, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2023-06-27 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 20:36 [PATCH v4 0/8] gdbstub: Add support for info proc mappings Ilya Leoshkevich
2023-06-21 20:36 ` [PATCH v4 1/8] linux-user: Expose do_guest_openat() and do_guest_readlink() Ilya Leoshkevich
2023-06-21 20:36 ` [PATCH v4 2/8] linux-user: Add "safe" parameter to do_guest_openat() Ilya Leoshkevich
2023-06-21 20:36 ` [PATCH v4 3/8] linux-user: Emulate /proc/self/smaps Ilya Leoshkevich
2023-06-21 20:36 ` [PATCH v4 4/8] gdbstub: Expose gdb_get_process() and gdb_get_first_cpu_in_process() Ilya Leoshkevich
2023-06-21 20:36 ` [PATCH v4 5/8] gdbstub: Report the actual qemu-user pid Ilya Leoshkevich
2023-06-21 20:36 ` [PATCH v4 6/8] gdbstub: Add support for info proc mappings Ilya Leoshkevich
2023-06-21 20:36 ` [PATCH v4 7/8] docs: Document security implications of debugging Ilya Leoshkevich
2023-06-21 20:36 ` [PATCH v4 8/8] tests/tcg: Add a test for info proc mappings Ilya Leoshkevich
2023-06-27 15:14 ` Alex Bennée [this message]
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=87h6qtym2j.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=david@redhat.com \
--cc=iii@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.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.