From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Fabiano Rosas" <farosas@suse.de>,
"Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"open list:Raspberry Pi" <qemu-arm@nongnu.org>
Subject: Re: [RFC PATCH] hw/dma: don't allow weird transfer lengths for bcm2835
Date: Tue, 11 Nov 2025 11:24:09 +0000 [thread overview]
Message-ID: <CAFEAcA_AUxECwpnfuoz28fUrwrMtbHxgesBwGscS_v3ocw4KPw@mail.gmail.com> (raw)
In-Reply-To: <20251111105429.3993300-1-alex.bennee@linaro.org>
On Tue, 11 Nov 2025 at 10:54, Alex Bennée <alex.bennee@linaro.org> wrote:
>
> The datasheet doesn't explicitly say that TXFR_LEN has to be word
> aligned but the fact there is a DMA_D_WIDTH flag to select between 32
> bit and 128 bit strongly implies that is how it works. The downstream
> rpi kernel also goes to efforts to not write sub-4 byte lengths so
> lets:
>
> - fail when mis-programmed and report GUEST_ERROR
> - catch setting D_WIDTH for 128 bit and report UNIMP
> - add comments that the DEBUG register isn't a straight write
>
> This includes the test case from the reported bug which is of unknown
> provenience but isn't particularly novel.
The emoji in the comment seems like a bit of a flag that
it might be AI-generated :-)
I would at least clean up the comments to be more in
line with our usual style and degree of detail.
thanks
-- PMM
next prev parent reply other threads:[~2025-11-11 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 10:54 [RFC PATCH] hw/dma: don't allow weird transfer lengths for bcm2835 Alex Bennée
2025-11-11 11:24 ` Peter Maydell [this message]
2025-11-14 16:05 ` Yodel Eldar
2025-11-14 16:15 ` Peter Maydell
2025-11-14 16:43 ` Alex Bennée
2025-11-14 16:51 ` Florian Kauer
2025-11-16 13:48 ` Yodel Eldar
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=CAFEAcA_AUxECwpnfuoz28fUrwrMtbHxgesBwGscS_v3ocw4KPw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--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).