qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org, "Jon Doron" <arilou@gmail.com>
Subject: [PULL v2 44/50] docs: Add to gdbstub documentation the PhyMemMode
Date: Sat, 11 Jul 2020 18:07:26 +0100	[thread overview]
Message-ID: <20200711170732.26213-5-alex.bennee@linaro.org> (raw)
In-Reply-To: <20200711170732.26213-1-alex.bennee@linaro.org>

From: Jon Doron <arilou@gmail.com>

The PhyMemMode gdb extension command was missing from the gdb.rst
document.

Signed-off-by: Jon Doron <arilou@gmail.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20200601171609.1665397-1-arilou@gmail.com>
Message-Id: <20200709141327.14631-4-alex.bennee@linaro.org>

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.
-- 
2.20.1



  parent reply	other threads:[~2020-07-11 17:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11 17:07 [PULL v2 00/50] testing updates (vm, gitlab, misc build fixes) Alex Bennée
2020-07-11 17:07 ` [PULL v2 04/50] tests/vm: Add configuration to basevm.py Alex Bennée
2020-07-11 17:07 ` [PULL v2 42/50] docs/devel: convert and update MTTCG design document Alex Bennée
2020-07-11 17:07 ` [PULL v2 43/50] docs/devel: add some notes on tcg-icount for developers Alex Bennée
2020-07-11 17:07 ` Alex Bennée [this message]
2020-07-11 17:07 ` [PULL v2 45/50] tests/docker: fall back more gracefully when pull fails Alex Bennée
2020-07-11 17:07 ` [PULL v2 46/50] tests/docker: update toolchain set in debian-xtensa-cross Alex Bennée
2020-07-11 17:07 ` [PULL v2 47/50] .cirrus.yml: add bash to the brew packages Alex Bennée
2020-07-11 17:07 ` [PULL v2 48/50] tests: fix "make check-qtest" for modular builds Alex Bennée
2020-07-11 17:07 ` [PULL v2 49/50] Revert "vga: build virtio-gpu as module" Alex Bennée
2020-07-11 17:07 ` [PULL v2 50/50] iotests: Set LC_ALL=C for sort Alex Bennée
2020-07-13  8:34 ` [PULL v2 00/50] testing updates (vm, gitlab, misc build fixes) Peter Maydell

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=20200711170732.26213-5-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=arilou@gmail.com \
    --cc=f4bug@amsat.org \
    --cc=peter.maydell@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).