From: Benno Lossin <benno.lossin@proton.me>
To: Lyude Paul <lyude@redhat.com>, rust-for-linux@vger.kernel.org
Cc: "Danilo Krummrich" <dakr@redhat.com>,
airlied@redhat.com, "Ingo Molnar" <mingo@redhat.com>,
"Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>
Subject: Re: [PATCH v2 0/3] rust: Add irq abstraction, SpinLockIrq
Date: Thu, 01 Aug 2024 09:39:14 +0000 [thread overview]
Message-ID: <0e9bd869-712c-4d1e-bd60-2cc5f18c8aac@proton.me> (raw)
In-Reply-To: <20240731224027.232642-1-lyude@redhat.com>
On 01.08.24 00:35, Lyude Paul wrote:
> This adds a simple interface for disabling and enabling CPUs, along with
> the ability to mark a function as expecting interrupts be disabled -
> along with adding bindings for spin_lock_irqsave/spin_lock_irqrestore().
>
> Current example usecase (very much WIP driver) in rvkms:
>
> https://gitlab.freedesktop.org/lyudess/linux/-/commits/rvkms-example-07312024
>
> specifically drivers/gpu/drm/rvkms/crtc.rs
>
> (The kunit tests also compile)
>
> Lyude Paul (3):
> rust: Introduce irq module
> rust: sync: Introduce lock::Backend::Context
> rust: sync: Add SpinLockIrq
>
> rust/helpers.c | 22 +++++++
> rust/kernel/irq.rs | 87 ++++++++++++++++++++++++
> rust/kernel/lib.rs | 1 +
> rust/kernel/sync.rs | 2 +-
> rust/kernel/sync/lock.rs | 17 ++++-
> rust/kernel/sync/lock/mutex.rs | 3 +
> rust/kernel/sync/lock/spinlock.rs | 106 ++++++++++++++++++++++++++++++
> 7 files changed, 235 insertions(+), 3 deletions(-)
> create mode 100644 rust/kernel/irq.rs
>
> --
> 2.45.2
>
Hi Lyude,
it would be nice if you could run `git format-patch` with `--base`. That
way I immediately have the commit that your series applies to. (Since this
series doesn't apply to `rust-next` for me, but it does apply to
v6.11-rc1, so it's fine)
Thanks.
---
Cheers,
Benno
prev parent reply other threads:[~2024-08-01 9:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 22:35 [PATCH v2 0/3] rust: Add irq abstraction, SpinLockIrq Lyude Paul
2024-07-31 22:35 ` [PATCH v2 1/3] rust: Introduce irq module Lyude Paul
2024-07-31 23:54 ` Lyude Paul
2024-08-01 9:51 ` Benno Lossin
2024-08-01 10:10 ` Benno Lossin
2024-08-01 16:44 ` Lyude Paul
2024-08-01 18:34 ` Benno Lossin
2024-08-01 18:37 ` Lyude Paul
2024-07-31 22:35 ` [PATCH v2 2/3] rust: sync: Introduce lock::Backend::Context Lyude Paul
2024-08-01 10:11 ` Benno Lossin
2024-08-01 16:52 ` Lyude Paul
2024-07-31 22:35 ` [PATCH v2 3/3] rust: sync: Add SpinLockIrq Lyude Paul
2024-08-01 10:29 ` Benno Lossin
2024-08-01 17:10 ` Lyude Paul
2024-08-01 18:38 ` Benno Lossin
2024-08-01 20:52 ` Lyude Paul
2024-08-01 21:44 ` Benno Lossin
2024-08-01 9:39 ` Benno Lossin [this message]
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=0e9bd869-712c-4d1e-bd60-2cc5f18c8aac@proton.me \
--to=benno.lossin@proton.me \
--cc=a.hindborg@samsung.com \
--cc=airlied@redhat.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@redhat.com \
--cc=gary@garyguo.net \
--cc=longman@redhat.com \
--cc=lyude@redhat.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
--cc=will@kernel.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).