From: "Alex Bennée" <alex.bennee@linaro.org>
To: Jon Doron <arilou@gmail.com>
Cc: qemu-trivial@nongnu.org, peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [v1] docs: Add to gdbstub documentation the PhyMemMode
Date: Tue, 07 Jul 2020 08:58:52 +0100 [thread overview]
Message-ID: <87fta3pxhf.fsf@linaro.org> (raw)
In-Reply-To: <20200601171609.1665397-1-arilou@gmail.com>
Jon Doron <arilou@gmail.com> writes:
> The PhyMemMode gdb extension command was missing from the gdb.rst
> document.
>
> Signed-off-by: Jon Doron <arilou@gmail.com>
Queued to docs/next, thanks.
> ---
> docs/system/gdb.rst | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/docs/system/gdb.rst b/docs/system/gdb.rst
> index a40145fcf8..abda961e2b 100644
> --- a/docs/system/gdb.rst
> +++ b/docs/system/gdb.rst
> @@ -87,3 +87,23 @@ three commands you can query and set the single step behavior:
> (gdb) maintenance packet Qqemu.sstep=0x5
> sending: "qemu.sstep=0x5"
> received: "OK"
> +
> +
> +Another feature that QEMU gdbstub provides is to toggle the memory GDB
> +works with, by default GDB will show the current process memory respecting
> +the virtual address translation.
> +
> +If you want to examine/change the physical memory you can set the gdbstub
> +to work with the physical memory rather with the virtual one.
> +
> +The memory mode can be checked by sending the following command:
> +
> +``maintenance packet qqemu.PhyMemMode``
> + This will return either 0 or 1, 1 indicates you are currently in the
> + physical memory mode.
> +
> +``maintenance packet Qqemu.PhyMemMode:1``
> + This will change the memory mode to physical memory.
> +
> +``maintenance packet Qqemu.PhyMemMode:0``
> + This will change it back to normal memory mode.
--
Alex Bennée
prev parent reply other threads:[~2020-07-07 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 17:16 [v1] docs: Add to gdbstub documentation the PhyMemMode Jon Doron
2020-07-07 7:58 ` 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=87fta3pxhf.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=arilou@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).