From: Richard Henderson <richard.henderson@linaro.org>
To: "Omair Javaid" <omair.javaid@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: mark.rutland@arm.com, Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
ard.biesheuvel@linaro.org
Subject: Re: [Qemu-devel] [PATCH v1 1/2] target/arm: kvm64 make guest debug AA32 break point aware
Date: Fri, 14 Dec 2018 07:53:06 -0600 [thread overview]
Message-ID: <d82faf0e-87d4-984a-0db8-558d4e8bda13@linaro.org> (raw)
In-Reply-To: <CANW4E-1UmZOGHya4jHxj10O2Ki7MPGMqme7wT0jaCO8Ufrii6g@mail.gmail.com>
On 12/14/18 2:37 AM, Omair Javaid wrote:
> Are you expecting GDB to switch targets (from AArch64 to AArch32 or
> vice versa) when there is mode switch for example a AArch64 binary
> calling a AArch32 library function.
Mode changes happen only at privilege level changes. E.g. AArch32 binary makes
a system call to an AArch64 kernel, or an AArch32 guest kernel takes an i/o
emulation trap to an AArch64 hypervisor.
But for this sort of system debugging, it would be nice to be able to
single-step through the whole operation.
r~
next prev parent reply other threads:[~2018-12-14 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 11:55 [Qemu-devel] [PATCH v1 0/2] Fix kvm guest debugging of AA32 guests on AA64 Alex Bennée
2018-12-13 11:55 ` [Qemu-devel] [PATCH v1 1/2] target/arm: kvm64 make guest debug AA32 break point aware Alex Bennée
2018-12-13 12:36 ` Ard Biesheuvel
2018-12-13 14:55 ` Alex Bennée
2018-12-13 22:25 ` Richard Henderson
2018-12-14 16:26 ` Alex Bennée
2018-12-14 16:40 ` Ard Biesheuvel
2018-12-13 22:21 ` Richard Henderson
2018-12-14 8:37 ` Omair Javaid
2018-12-14 13:53 ` Richard Henderson [this message]
2018-12-13 11:55 ` [Qemu-devel] [PATCH v1 2/2] target/arm: defer setting up of aarch64 gdb until arm_cpu_realize Alex Bennée
2018-12-13 23:10 ` Richard Henderson
2019-01-04 15:35 ` Peter Maydell
2019-01-07 8:49 ` Alex Bennée
2018-12-13 11:57 ` [Qemu-devel] [PATCH v1 0/2] Fix kvm guest debugging of AA32 guests on AA64 Mark Rutland
2018-12-13 15:28 ` Alex Bennée
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=d82faf0e-87d4-984a-0db8-558d4e8bda13@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=ard.biesheuvel@linaro.org \
--cc=mark.rutland@arm.com \
--cc=omair.javaid@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).