From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 1/5] hw/intc/arm_gicv3_its: Add trace events for commands
Date: Thu, 3 Mar 2022 11:40:07 -1000 [thread overview]
Message-ID: <835773ab-91d8-49de-7ab5-d2e2e528c6b8@linaro.org> (raw)
In-Reply-To: <20220303202341.2232284-2-peter.maydell@linaro.org>
On 3/3/22 10:23, Peter Maydell wrote:
> When debugging code that's using the ITS, it's helpful to
> see tracing of the ITS commands that the guest executes. Add
> suitable trace events.
>
> Signed-off-by: Peter Maydell<peter.maydell@linaro.org>
> ---
> hw/intc/arm_gicv3_its.c | 28 ++++++++++++++++++++++++++--
> hw/intc/trace-events | 12 ++++++++++++
> 2 files changed, 38 insertions(+), 2 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2022-03-03 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 20:23 [PATCH 0/5] arm gicv3: minor bug fixes, ITS trace events Peter Maydell
2022-03-03 20:23 ` [PATCH 1/5] hw/intc/arm_gicv3_its: Add trace events for commands Peter Maydell
2022-03-03 21:40 ` Richard Henderson [this message]
2022-03-03 20:23 ` [PATCH 2/5] hw/intc/arm_gicv3_its: Add trace events for table reads and writes Peter Maydell
2022-03-03 21:41 ` Richard Henderson
2022-03-03 20:23 ` [PATCH 3/5] hw/intc/arm_gicv3: Specify valid and impl in MemoryRegionOps Peter Maydell
2022-03-03 21:42 ` Richard Henderson
2022-03-03 20:23 ` [PATCH 4/5] hw/intc/arm_gicv3: Fix missing spaces in error log messages Peter Maydell
2022-03-03 21:43 ` Richard Henderson
2022-03-03 20:23 ` [PATCH 5/5] hw/intc/arm_gicv3_cpuif: Fix register names in ICV_HPPIR read trace event Peter Maydell
2022-03-03 21:45 ` Richard Henderson
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=835773ab-91d8-49de-7ab5-d2e2e528c6b8@linaro.org \
--to=richard.henderson@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).