From: Jon Doron <arilou@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Edgar E . Iglesias" <edgar.iglesias@xilinx.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Luc Michel" <luc.michel@greensocs.com>
Subject: Re: [PATCH-for-5.0] gdbstub: Use correct address space with Qqemu.PhyMemMode packet
Date: Mon, 1 Jun 2020 13:41:57 +0300 [thread overview]
Message-ID: <20200601104157.GH3071@jondnuc> (raw)
In-Reply-To: <87r1uz6pe7.fsf@linaro.org>
On 01/06/2020, Alex Bennée wrote:
>
>Jon Doron <arilou@gmail.com> writes:
>
>> On 31/05/2020, Peter Maydell wrote:
>>>On Sun, 31 May 2020 at 17:42, Jon Doron <arilou@gmail.com> wrote:
>>>>
>>>> On 31/05/2020, Philippe Mathieu-Daudé wrote:
>>>> >On 3/30/20 6:41 PM, Peter Maydell wrote:
>>>> >> PS: do we have any documentation of this new command ?
>>>> >> ab4752ec8d9 has the implementation but no documentation...
>>>> >
>>>> >Jon, do you have documentation on the Qqemu.PhyMemMode packet?
>>>
>>>> Hi, there is no documentation for this mode, but in general the idea was
>>>> very simple.
>>>>
>>>> I want to have GDB the option to see the physical memory and examine it
>>>> and have this option toggled.
>>>>
>>>> This was useful to me when I was working on nested virtual machine and I
>>>> wanted to examine different states of the VMCS12 and EPTs.
>>>>
>>>> I used this in the following commands:
>>>> // Enable
>>>> maint packet Qqemu.PhyMemMode:1
>>>>
>>>> // Disable
>>>> maint packet Qqemu.PhyMemMode:0
>>>
>>>docs/system/gdb.rst would be the place to document QEMU-specific
>>>extensions to the gdb protocol (there's an "advanced debugging
>>>options" section where we document things like the single-step
>>>stuff you can also change via 'maint packet').
>>>
>>>thanks
>>>-- PMM
>>
>> Thanks, I'll know for next time, when I did all that work and
>> re-factored gdbstub, that doc did not exist.
>
>The documentation existed in our old texinfo docs, however they have
>been recently updated to rst and are now considerably easier to find and
>hack on now.
>
>> Perhaps Peter can just add the documentation to this commit?
>
>Please don't impose extra burden on our overworked maintainer when he's
>already given review feedback. Generally maintainers have more work to
>do than time to do it in so the easiest way to expedite patches with
>features you want added is to send well formed complete patches which
>can be easily merged. Otherwise patches tend to end up deep in a pile of
>"must get around to that when I can".
>
>--
>Alex Bennée
No problem, I'll revise a patch to the rst and send it.
Thanks,
-- Jon.
prev parent reply other threads:[~2020-06-01 10:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 15:30 [PATCH-for-5.0] gdbstub: Use correct address space with Qqemu.PhyMemMode packet Philippe Mathieu-Daudé
2020-03-30 16:08 ` Peter Maydell
2020-03-30 16:21 ` Philippe Mathieu-Daudé
2020-03-30 16:41 ` Peter Maydell
2020-05-31 15:27 ` Philippe Mathieu-Daudé
2020-05-31 16:42 ` Jon Doron
2020-05-31 16:57 ` Peter Maydell
2020-06-01 7:29 ` Jon Doron
2020-06-01 10:39 ` Alex Bennée
2020-06-01 10:41 ` Jon Doron [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=20200601104157.GH3071@jondnuc \
--to=arilou@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=edgar.iglesias@xilinx.com \
--cc=f4bug@amsat.org \
--cc=luc.michel@greensocs.com \
--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).