From: "Alex Bennée" <alex.bennee@linaro.org>
To: Libo Zhou <zhlb29@foxmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Subject: Re: [Qemu-devel] QEMU as ISS (Instruction Set Simulator)
Date: Thu, 12 Sep 2019 12:41:25 +0100 [thread overview]
Message-ID: <87h85hzqqi.fsf@linaro.org> (raw)
In-Reply-To: <tencent_0E8715864EBBAA153BB730E2@qq.com>
Libo Zhou <zhlb29@foxmail.com> writes:
> Alex Bennée <alex.bennee@linaro.org> writes:
>
>
>> The gdbstub should allow you do full introspection and adding
>> additional registers is fairly easy, see mips_cpu_gdb_read_register function
>> in target/mips/gdbstub.c.
>
>
>
> Hi Alex and Aleksandar,
>
>
> Now I can connect gdb to qemu successfully. And I can use this command
> to show all the register contents in a gdb session.
You will need to update gdb-xml/$ARCH.xml and the appropriate
arch_read/write register functions in gdbstub.
Alternatively look at commits:
commit 200bf5b7ffea635079cc05fdfb363372b9544ce7
Author: Abdallah Bouassida <abdallah.bouassida@lauterbach.com>
commit 9c513e786d85cc58b8ba56a482566f759e0835b6
Author: Abdallah Bouassida <abdallah.bouassida@lauterbach.com>
commit 1f16378718fa87d63f70d0797f4546a88d8e3dd7
Author: Abdallah Bouassida <abdallah.bouassida@lauterbach.com>
Where Abdallah added a dynamic xml generation to expose all the ARM
system registers to gdbstub. The details may be different for the MIPS
backend but from the gdbstub point of view its the same. Provide a
system description in xml and the arch specific helpers to get and set
the values.
>
>
> (gdb) layout regs
>
>
> However, I will need to add some more registers to the CPU. Does adding new registers in gdbstub.c also show the new registers in the TUI?
> I doubt it because when I modified the regnames[] in translate.c, the registers' names didn't change in gdb.
>
>
>
> Cheers,
> Libo
>
>
>
>> Alex Bennée
--
Alex Bennée
next prev parent reply other threads:[~2019-09-12 11:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 3:23 [Qemu-devel] QEMU as ISS (Instruction Set Simulator) Libo Zhou
2019-09-05 10:54 ` Aleksandar Markovic
2019-09-05 11:57 ` Libo Zhou
2019-09-05 12:58 ` Alex Bennée
[not found] ` <tencent_541F04AB1A100DF25C334D8C@qq.com>
2019-09-06 9:19 ` Alex Bennée
[not found] ` <tencent_479D109A5BEC536D64AE43BF@qq.com>
2019-09-10 12:10 ` Alex Bennée
2019-09-10 17:27 ` Aleksandar Markovic
2019-09-10 17:50 ` Aleksandar Markovic
2019-09-11 8:48 ` Libo Zhou
2019-09-11 13:09 ` Aleksandar Markovic
2019-09-12 10:28 ` Libo Zhou
2019-09-12 11:41 ` Alex Bennée [this message]
2019-09-18 4:08 ` Libo Zhou
-- strict thread matches above, loose matches on Subject: below --
2019-08-30 9:14 =?gb18030?B?TGlibyBaaG91?=
2019-09-03 7:07 ` Aleksandar Markovic
2019-08-20 10:11 =?gb18030?B?waI=?=
2019-08-20 10:20 ` Peter Maydell
2019-08-20 10:42 ` Aleksandar Markovic
2019-08-22 8:23 ` Aleksandar Markovic
2019-08-22 10:24 ` =?gb18030?B?waI=?=
2019-08-22 10:53 ` Aleksandar Markovic
2019-08-28 3:54 ` =?gb18030?B?TGlibyBaaG91?=
2019-08-29 14:22 ` Aleksandar Markovic
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=87h85hzqqi.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aleksandar.m.mail@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=zhlb29@foxmail.com \
/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).