From: Lee Jones <lee@kernel.org>
To: "Benoît du Garreau" <benoit@dugarreau.fr>
Cc: linux-kernel@vger.kernel.org, ojeda@kernel.org,
alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, benno.lossin@proton.me,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
rust-for-linux@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 1/2] samples: rust: Provide example using the new Rust MiscDevice abstraction
Date: Thu, 5 Dec 2024 09:46:10 +0000 [thread overview]
Message-ID: <20241205094610.GH7451@google.com> (raw)
In-Reply-To: <20241205092135.48978-1-benoit@dugarreau.fr>
On Thu, 05 Dec 2024, Benoît du Garreau wrote:
> On Wed, 4 Dec 2024 17:46:24 +0000 Lee Jones <lee@kernel.org> wrote:
>
> > This sample driver demonstrates the following basic operations:
> >
> > * Register a Misc Device
> > * Create /dev/rust-misc-device
> > * Open the aforementioned character device
> > * Operate on the character device via a simple ioctl()
> > * Close the character device
> >
> > Signed-off-by: Lee Jones <lee@kernel.org>
> > ---
> > samples/rust/Kconfig | 10 ++++
> > samples/rust/Makefile | 1 +
> > samples/rust/rust_misc_device.rs | 84 ++++++++++++++++++++++++++++++++
> > 3 files changed, 95 insertions(+)
> > create mode 100644 samples/rust/rust_misc_device.rs
> >
> > diff --git a/samples/rust/Kconfig b/samples/rust/Kconfig
> > index b0f74a81c8f9..df384e679901 100644
> > --- a/samples/rust/Kconfig
> > +++ b/samples/rust/Kconfig
> > @@ -20,6 +20,16 @@ config SAMPLE_RUST_MINIMAL
> >
> > If unsure, say N.
> >
> > +config SAMPLE_RUST_MISC_DEVICE
> > + tristate "Misc device"
> > + help
> > + This option builds the Rust misc device.
> > +
> > + To compile this as a module, choose M here:
> > + the module will be called rust_misc_device.
> > +
> > + If unsure, say N.
> > +
> > config SAMPLE_RUST_PRINT
> > tristate "Printing macros"
> > help
> > diff --git a/samples/rust/Makefile b/samples/rust/Makefile
> > index c1a5c1655395..ad4b97a98580 100644
> > --- a/samples/rust/Makefile
> > +++ b/samples/rust/Makefile
> > @@ -2,6 +2,7 @@
> > ccflags-y += -I$(src) # needed for trace events
> >
> > obj-$(CONFIG_SAMPLE_RUST_MINIMAL) += rust_minimal.o
> > +obj-$(CONFIG_SAMPLE_RUST_MISC_DEVICE) += rust_misc_device.o
> > obj-$(CONFIG_SAMPLE_RUST_PRINT) += rust_print.o
> >
> > rust_print-y := rust_print_main.o rust_print_events.o
> > diff --git a/samples/rust/rust_misc_device.rs b/samples/rust/rust_misc_device.rs
> > new file mode 100644
> > index 000000000000..5f1b69569ef7
> > --- /dev/null
> > +++ b/samples/rust/rust_misc_device.rs
> > @@ -0,0 +1,84 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +
> > +//! Rust misc device sample.
> > +
> > +use kernel::{
> > + c_str,
> > + ioctl::_IO,
> > + miscdevice::{MiscDevice, MiscDeviceOptions, MiscDeviceRegistration},
> > + prelude::*,
> > +};
> > +
> > +const RUST_MISC_DEV_HELLO: u32 = _IO('R' as u32, 9);
> > +
> > +module! {
> > + type: RustMiscDeviceModule,
> > + name: "rust_misc_device",
> > + author: "Lee Jones",
> > + description: "Rust misc device sample",
> > + license: "GPL",
> > +}
> > +
> > +struct RustMiscDeviceModule {
> > + _miscdev: Pin<KBox<MiscDeviceRegistration<RustMiscDevice>>>,
> > +}
> > +
> > +impl kernel::Module for RustMiscDeviceModule {
>
> This could probably use `kernel::InPlaceModule` and avoid allocating
> the registration.
Is there a way to do this and keep the print?
> > + fn init(_module: &'static ThisModule) -> Result<Self> {
> > + pr_info!("Initialising Rust Misc Device Sample\n");
> > +
> > + let options = MiscDeviceOptions {
> > + name: c_str!("rust-misc-device"),
> > + };
> > +
> > + Ok(Self {
> > + _miscdev: KBox::pin_init(
> > + MiscDeviceRegistration::<RustMiscDevice>::register(options),
> > + GFP_KERNEL,
> > + )?,
> > + })
> > + }
> > +}
> > +
> > +struct RustMiscDevice;
> > +
> > +impl RustMiscDevice {
> > + fn new() -> Self {
> > + Self
> > + }
> > +}
>
> Given that this function is nearly empty and removed in the next commit,
> it could probably not exist in the first place.
This is showing my Rust immaturity here.
How does one create a new Self without new() in this context?
> > +
> > +#[vtable]
> > +impl MiscDevice for RustMiscDevice {
> > + type Ptr = KBox<Self>;
> > +
> > + fn open() -> Result<KBox<Self>> {
> > + pr_info!("Opening Rust Misc Device Sample\n");
> > +
> > + Ok(KBox::new(RustMiscDevice::new(), GFP_KERNEL)?)
> > + }
> > +
> > + fn ioctl(
> > + _device: <Self::Ptr as kernel::types::ForeignOwnable>::Borrowed<'_>,
> > + cmd: u32,
> > + _arg: usize,
> > + ) -> Result<isize> {
> > + pr_info!("IOCTLing Rust Misc Device Sample\n");
> > +
> > + match cmd {
> > + RUST_MISC_DEV_HELLO => pr_info!("Hello from the Rust Misc Device\n"),
> > + _ => {
> > + pr_err!("IOCTL not recognised: {}\n", cmd);
> > + return Err(EINVAL);
> > + }
> > + }
> > +
> > + Ok(0)
> > + }
> > +}
> > +
> > +impl Drop for RustMiscDevice {
> > + fn drop(&mut self) {
> > + pr_info!("Exiting the Rust Misc Device Sample\n");
> > + }
> > +}
> > --
> > 2.47.0.338.g60cca15819-goog
>
>
> Benoît du Garreau
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2024-12-05 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 17:46 [PATCH 1/2] samples: rust: Provide example using the new Rust MiscDevice abstraction Lee Jones
2024-12-04 17:46 ` [PATCH 2/2] sample: rust_misc_device: Demonstrate additional get/set value functionality Lee Jones
2024-12-04 18:25 ` Greg KH
2024-12-05 8:38 ` Lee Jones
2024-12-05 9:01 ` Greg KH
2024-12-05 9:27 ` Lee Jones
2024-12-05 9:47 ` Greg KH
2024-12-09 21:34 ` Miguel Ojeda
2024-12-04 18:20 ` [PATCH 1/2] samples: rust: Provide example using the new Rust MiscDevice abstraction Greg KH
2024-12-05 8:41 ` Lee Jones
2024-12-05 9:03 ` Greg KH
2024-12-05 9:17 ` Lee Jones
2024-12-05 9:26 ` Greg KH
2024-12-05 9:21 ` Benoît du Garreau
2024-12-05 9:46 ` Lee Jones [this message]
2024-12-05 10:03 ` Lee Jones
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=20241205094610.GH7451@google.com \
--to=lee@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=benoit@dugarreau.fr \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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