From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: laurent@vivier.eu
Cc: jserv@ccns.ncku.edu.tw, qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/misc/virt_ctrl: Fix incorrect trace event in read operation
Date: Mon, 23 Feb 2026 01:55:20 +0800 [thread overview]
Message-ID: <aZtDCIujj1OC-ol0@google.com> (raw)
In-Reply-To: <20260111184915.1363318-1-visitorckw@gmail.com>
Hi Laurent,
On Sun, Jan 11, 2026 at 06:49:15PM +0000, Kuan-Wei Chiu wrote:
> The virt_ctrl_read() function currently invokes trace_virt_ctrl_write()
> instead of trace_virt_ctrl_read(). This results in read operations
> appearing as write operations in the trace output, which is misleading
> during debugging and analysis.
>
> Replace the incorrect trace call with the proper read-specific trace
> event to accurately reflect the hardware behavior.
>
> Fixes: 0791bc02b8fb ("m68k: add a system controller")
> Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
> ---
> hw/misc/virt_ctrl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Any comments on this patch?
Regards,
Kuan-Wei
>
> diff --git a/hw/misc/virt_ctrl.c b/hw/misc/virt_ctrl.c
> index 40747925a2..9b82e97ffd 100644
> --- a/hw/misc/virt_ctrl.c
> +++ b/hw/misc/virt_ctrl.c
> @@ -43,7 +43,7 @@ static uint64_t virt_ctrl_read(void *opaque, hwaddr addr, unsigned size)
> break;
> }
>
> - trace_virt_ctrl_write(s, addr, size, value);
> + trace_virt_ctrl_read(s, addr, size, value);
>
> return value;
> }
> --
> 2.52.0.457.g6b5491de43-goog
>
next prev parent reply other threads:[~2026-02-22 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 18:49 [PATCH] hw/misc/virt_ctrl: Fix incorrect trace event in read operation Kuan-Wei Chiu
2026-02-22 17:55 ` Kuan-Wei Chiu [this message]
2026-02-22 21:45 ` Philippe Mathieu-Daudé
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=aZtDCIujj1OC-ol0@google.com \
--to=visitorckw@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=laurent@vivier.eu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.