From: Fea Wang <fea.wang@sifive.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Alistair Francis <alistair@alistair23.me>,
Peter Maydell <peter.maydell@linaro.org>,
Jason Wang <jasowang@redhat.com>,
"open list:Xilinx Zynq" <qemu-arm@nongnu.org>,
"Edgar E . Iglesias" <edgar.iglesias@amd.com>,
Frank Chang <frank.chang@sifive.com>
Subject: Re: [PATCH v2 2/3] hw/dma: Add a trace log for a description loading failure
Date: Thu, 13 Jun 2024 09:24:11 +0800 [thread overview]
Message-ID: <CAKhCfsfarBTCud3Bo8e3viNxQMLT0X+xQSpPACMyPFgOECB-8g@mail.gmail.com> (raw)
In-Reply-To: <3a919e08-fcce-48d5-b609-cc97cd3ff22b@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
Sure, I will fix it in the next patch series.
Thank you
Sincerely,
Fea
On Mon, Jun 10, 2024 at 7:49 PM Philippe Mathieu-Daudé <philmd@linaro.org>
wrote:
> Hi Fea,
>
> On 4/6/24 09:15, Fea.Wang wrote:
> > Due to a description loading failure, adding a trace log makes observing
> > the DMA behavior easy.
> >
> > Signed-off-by: Fea.Wang <fea.wang@sifive.com>
> > Reviewed-by: Edgar E. Iglesias <edgar.iglesias@amd.com>
> > Reviewed-by: Frank Chang <frank.chang@sifive.com>
> > ---
> > hw/dma/trace-events | 3 +++
> > hw/dma/xilinx_axidma.c | 3 +++
> > 2 files changed, 6 insertions(+)
>
>
> > +# xilinx_axidma.c
> > +xilinx_axidma_loading_desc_fail(uint32_t res) "error:%d"
>
> Unsigned format is "%u".
>
> Regards,
>
> Phil.
>
[-- Attachment #2: Type: text/html, Size: 1407 bytes --]
next prev parent reply other threads:[~2024-06-13 1:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 7:15 [PATCH v2 0/3] hw/dma: Add error handling for loading descriptions failing Fea.Wang
2024-06-04 7:15 ` [PATCH v2 1/3] hw/dma: Enhance error handling in loading description Fea.Wang
2024-06-06 11:55 ` Edgar E. Iglesias
2024-06-04 7:15 ` [PATCH v2 2/3] hw/dma: Add a trace log for a description loading failure Fea.Wang
2024-06-10 11:48 ` Philippe Mathieu-Daudé
2024-06-13 1:24 ` Fea Wang [this message]
2024-06-04 7:15 ` [PATCH v2 3/3] hw/net: Fix the transmission return size Fea.Wang
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=CAKhCfsfarBTCud3Bo8e3viNxQMLT0X+xQSpPACMyPFgOECB-8g@mail.gmail.com \
--to=fea.wang@sifive.com \
--cc=alistair@alistair23.me \
--cc=edgar.iglesias@amd.com \
--cc=edgar.iglesias@gmail.com \
--cc=frank.chang@sifive.com \
--cc=jasowang@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@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).