From: Igor Mammedov <imammedo@redhat.com>
To: David Hoppenbrouwers <qemu@demindiro.com>
Cc: qemu-devel@nongnu.org, Eduardo Habkost <eduardo@habkost.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
Sairaj Kodilkar <sarunkod@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] hw/i386/amd_iommu.c: fix amdvi_unhandled_command logging cmd ID
Date: Mon, 23 Feb 2026 08:32:57 +0100 [thread overview]
Message-ID: <20260223083257.423660c4@imammedo> (raw)
In-Reply-To: <20260220181437.19338-1-qemu@demindiro.com>
On Fri, 20 Feb 2026 19:14:37 +0100
David Hoppenbrouwers <qemu@demindiro.com> wrote:
> The command ID is in cmd[0], not cmd[1].
pls add a reference to the spec,
and if any what impact it does have on a guest/how it manifests.
> Signed-off-by: David Hoppenbrouwers <qemu@demindiro.com>
> ---
> hw/i386/amd_iommu.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/i386/amd_iommu.c b/hw/i386/amd_iommu.c
> index 789e09d6f2..2570a4701c 100644
> --- a/hw/i386/amd_iommu.c
> +++ b/hw/i386/amd_iommu.c
> @@ -1456,9 +1456,9 @@ static void amdvi_cmdbuf_exec(AMDVIState *s)
> amdvi_inval_all(s, cmd);
> break;
> default:
> - trace_amdvi_unhandled_command(extract64(cmd[1], 60, 4));
> + trace_amdvi_unhandled_command(extract64(cmd[0], 60, 4));
> /* log illegal command */
> - amdvi_log_illegalcom_error(s, extract64(cmd[1], 60, 4),
> + amdvi_log_illegalcom_error(s, extract64(cmd[0], 60, 4),
> s->cmdbuf + s->cmdbuf_head);
> }
> }
next prev parent reply other threads:[~2026-02-23 7:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 18:14 [PATCH] hw/i386/amd_iommu.c: fix amdvi_unhandled_command logging cmd ID David Hoppenbrouwers
2026-02-23 7:32 ` Igor Mammedov [this message]
2026-02-23 13:06 ` David Hoppenbrouwers
2026-02-23 18:49 ` Alejandro Jimenez
2026-02-24 11:46 ` Igor Mammedov
2026-02-24 17:28 ` David Hoppenbrouwers
2026-02-23 8:15 ` Sairaj Kodilkar
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=20260223083257.423660c4@imammedo \
--to=imammedo@redhat.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu@demindiro.com \
--cc=richard.henderson@linaro.org \
--cc=sarunkod@amd.com \
/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.