From: "Libo Zhou" <zhlb29@foxmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
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: Wed, 18 Sep 2019 12:08:03 +0800 [thread overview]
Message-ID: <tencent_58B0F07F365894E75B3A12FC@qq.com> (raw)
In-Reply-To: <87h85hzqqi.fsf@linaro.org>
Alex Bennée writes:
> You will need to update gdb-xml/$ARCH.xml and the appropriate
arch_read/write register functions in gdbstub.
For some mysterious reason my previous emails didn't go to the list successfully. Let me try sending this one without including any code or link.
The MIPS target doesn't have mips*.xml, so I tried implementing it myself. As per the "Standard Target Features" requirement by GDB, I created mips-cpu.xml, mips-cp0.xml, mips-fpu.xml, and finally included them all in a wrapper mips.xml. Essentially I followed this commit: b8158192fadb3e346372456c25cbbc4be584a85c. (Yes it failed because <feature> is nested in <feature>, so I nest <feature> in <target>.)
Unfortunately, it doesn't work. GDB just doesn't recognize my change. It still displays the default reg names (zero, at, v0, v1, a0, a1, etc.), but I want my r0, r1, ... r31.
So, I went to the i386 target, whose gdbstub is working properly, and tweaked with its xml to see if changing xml reg names reflects in GDB session. However, when I changed "rax" to "zax", GDB gave me a 'g' packet error. I am really stuck at this point.
I really want to post my git diff below, but let's see if my mail can go to the list this time. Sorry for the inconvenience.
Cheers,
Libo Zhou
P.S. The dynamic xml generation option is too difficult for me for now. I will save it as an alternative in the future.
next prev parent reply other threads:[~2019-09-18 4:16 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
2019-09-18 4:08 ` Libo Zhou [this message]
-- 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=tencent_58B0F07F365894E75B3A12FC@qq.com \
--to=zhlb29@foxmail.com \
--cc=aleksandar.m.mail@gmail.com \
--cc=alex.bennee@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).