From: Abdiel Janulgue <abdiel.janulgue@gmail.com>
To: rust-for-linux@vger.kernel.org
Cc: aliceryhl@google.com, daniel.almeida@collabora.com,
a.hindborg@kernel.org, dakr@redhat.com, airlied@redhat.com,
miguel.ojeda.sandonis@gmail.com, wedsonaf@gmail.com,
a.hindborg@samsung.com,
Abdiel Janulgue <abdiel.janulgue@gmail.com>
Subject: [PATCH v4 0/2] Add dma coherent allocator abstraction
Date: Tue, 5 Nov 2024 12:46:55 +0200 [thread overview]
Message-ID: <20241105104726.3111058-1-abdiel.janulgue@gmail.com> (raw)
This series adds support for the dma coherent allocator.
Changs since v3:
- Reject ZST types by checking the type size in the constructor in
addition to requiring FromBytes/AsBytes traits for the type (Alice Ryhl).
Changes since v2:
- Fixed missing header for generating the bindings.
Changes since v1:
- Fix missing info in commit log where EOVERFLOW is used
- Restrict the dma coherent allocator to numeric types for now for valid
behaviour (Daniel Almeida).
- Build slice dynamically.
Abdiel Janulgue (2):
rust: error: Add EOVERFLOW
rust: add dma coherent allocator abstraction.
rust/bindings/bindings_helper.h | 1 +
rust/kernel/dma.rs | 169 ++++++++++++++++++++++++++++++++
rust/kernel/error.rs | 1 +
rust/kernel/lib.rs | 1 +
4 files changed, 172 insertions(+)
create mode 100644 rust/kernel/dma.rs
base-commit: ae7851c29747fa3765ecb722fe722117a346f988
--
2.43.0
next reply other threads:[~2024-11-05 10:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 10:46 Abdiel Janulgue [this message]
2024-11-05 10:46 ` [PATCH v4 1/2] rust: error: Add EOVERFLOW Abdiel Janulgue
2024-11-05 10:46 ` [PATCH v4 2/2] rust: add dma coherent allocator abstraction Abdiel Janulgue
2024-11-05 11:23 ` Miguel Ojeda
2024-11-06 8:47 ` Abdiel Janulgue
2024-11-06 10:21 ` Dirk Behme
2024-11-06 11:25 ` Miguel Ojeda
2024-11-06 16:40 ` Daniel Almeida
2024-11-07 13:01 ` Abdiel Janulgue
2024-11-09 23:42 ` Daniel Almeida
2024-11-11 10:48 ` Abdiel Janulgue
2024-11-11 12:55 ` Andreas Hindborg
2024-11-11 12:59 ` Abdiel Janulgue
2024-11-05 11:23 ` [PATCH v4 0/2] Add " Miguel Ojeda
2024-11-06 8:47 ` Abdiel Janulgue
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=20241105104726.3111058-1-abdiel.janulgue@gmail.com \
--to=abdiel.janulgue@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=a.hindborg@samsung.com \
--cc=airlied@redhat.com \
--cc=aliceryhl@google.com \
--cc=dakr@redhat.com \
--cc=daniel.almeida@collabora.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.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 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).