From: Joe Komlodi <joe.komlodi@xilinx.com>
To: qemu-devel@nongnu.org
Cc: edgar.iglesias@xilinx.com
Subject: [PATCH v1 0/4] target/microblaze: Add dynamic GDB XML and correct SReg reporting
Date: Mon, 11 May 2020 10:05:47 -0700 [thread overview]
Message-ID: <1589216751-106038-1-git-send-email-komlodi@xilinx.com> (raw)
Hi all,
This series adds dynamic GDB XML support for Micraoblaze CPUs, and fixes
an issue when reporting Microblaze SRegs through GDB.
The SRegs used to be printed out by iterating over the SReg array, but the
SReg array isn't laid out in memory in the same order that GDB expects them.
When reporting register to GDB, note that even though 32-bit Microblaze
supports having certain registers wider than 32-bits, we're repoting all of
them as being 32-bits wide right now to maintain compatibility with GDB.
Thanks!
Joe
Joe Komlodi (4):
target/microblaze: gdb: Add dynamic GDB XML register support
target/microblaze: gdb: Extend the number of registers presented to
GDB
target/microblaze: gdb: Fix incorrect SReg reporting
target/microblaze: monitor: Increase the number of registers reported
configure | 1 +
target/microblaze/cpu.c | 6 +-
target/microblaze/cpu.h | 9 ++
target/microblaze/gdbstub.c | 214 +++++++++++++++++++++++++++++++++++++++++-
target/microblaze/translate.c | 16 +++-
5 files changed, 240 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2020-05-11 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 17:05 Joe Komlodi [this message]
2020-05-11 17:05 ` [PATCH v1 1/4] target/microblaze: gdb: Add dynamic GDB XML register support Joe Komlodi
2020-05-11 17:05 ` [PATCH v1 2/4] target/microblaze: gdb: Extend the number of registers presented to GDB Joe Komlodi
2020-05-11 17:05 ` [PATCH v1 3/4] target/microblaze: gdb: Fix incorrect SReg reporting Joe Komlodi
2020-05-11 17:05 ` [PATCH v1 4/4] target/microblaze: monitor: Increase the number of registers reported Joe Komlodi
2020-05-13 11:46 ` [PATCH v1 0/4] target/microblaze: Add dynamic GDB XML and correct SReg reporting Edgar E. Iglesias
2020-05-13 17:28 ` Edgar E. Iglesias
2020-05-13 17:56 ` Joe Komlodi
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=1589216751-106038-1-git-send-email-komlodi@xilinx.com \
--to=joe.komlodi@xilinx.com \
--cc=edgar.iglesias@xilinx.com \
--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).