All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kunwu Chan <kunwu.chan@linux.dev>
To: Alice Ryhl <aliceryhl@google.com>
Cc: 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, tmgross@umich.edu,
	dakr@kernel.org, nathan@kernel.org,
	nick.desaulniers+lkml@gmail.com, morbo@google.com,
	justinstitt@google.com, rust-for-linux@vger.kernel.org,
	linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	Kunwu Chan <kunwu.chan@hotmail.com>,
	Grace Deng <Grace.Deng006@gmail.com>
Subject: Re: [PATCH] rust: file: optimize rust symbol generation for FileDescriptorReservation
Date: Fri, 14 Mar 2025 10:33:22 +0800	[thread overview]
Message-ID: <6c874a4f-439e-4ab2-807d-d0f59b9fe569@linux.dev> (raw)
In-Reply-To: <Z9K3vokYu5osMCwh@google.com>

On 2025/3/13 18:47, Alice Ryhl wrote:
> On Thu, Mar 13, 2025 at 04:45:25PM +0800, Kunwu Chan wrote:
>> From: Kunwu Chan <kunwu.chan@hotmail.com>
>>
>> When build the kernel using the llvm-18.1.3-rust-1.85.0-x86_64
>> with ARCH=arm64, the following symbols are generated:
>>
>> $ nm vmlinux | grep ' _R'.*FileDescriptorReservation | rustfilt
>> ffff8000805b6ef0 T <kernel::fs::file::FileDescriptorReservation>
>> 						::fd_install
>> ffff8000805b6e60 T <kernel::fs::file::FileDescriptorReservation>
>> 						::get_unused_fd_flags
>> ffff8000805b6f08 T <kernel::fs::file::FileDescriptorReservation
>> 					 as core::ops::drop::Drop>::drop
>>
>> These Rust symbols are trivial wrappers around the C functions
>> fd_install, put_unused_fd and put_task_struct.It
>> doesn't make sense to go through a trivial wrapper for these
>> functions, so mark them inline.
>>
>> After doing so, the above symbol will not in output.
>>
>> Signed-off-by: Kunwu Chan <kunwu.chan@hotmail.com>
>> Co-developed-by: Grace Deng <Grace.Deng006@Gmail.com>
>> Signed-off-by: Grace Deng <Grace.Deng006@Gmail.com>
> A few notes:
>
> * Your own Signed-off-by must always be last.
> * You're missing Link: and Suggested-by: tags.

Thanks for the reply.

I'll change my own Signed-off-by be last and add Link and Suggested-by 
as the following:

Link: https://github.com/Rust-for-Linux/linux/issues/1145
Suggested-by: Alice Ryhl <aliceryhl@google.com>
Co-developed-by: Grace Deng <Grace.Deng006@Gmail.com>
Signed-off-by: Grace Deng <Grace.Deng006@Gmail.com>
Signed-off-by: Kunwu Chan <kunwu.chan@hotmail.com>

> * There are some grammar issues, e.g. a missing space before "It" and
>    the phrase "will not in output" is not good.
I'll  add a space before "It" and remove the last line.
> * Let's also add the marker to `reserved_fd` to be on the safe side.
Sure, I'll make 'reserved_fd ' inline in v2.
> * I think it is easier to read the symbols if you list each sybmol on
>    one line like this:
>
> ffff8000805b6ef0 T <kernel::fs::file::FileDescriptorReservation>::fd_install
> ffff8000805b6e60 T <kernel::fs::file::FileDescriptorReservation>::get_unused_fd_flags
> ffff8000805b6f08 T <kernel::fs::file::FileDescriptorReservation as core::ops::drop::Drop>::drop

If in one line, checkpatch.pl will report a warning:

WARNING:Prefer a maximum 75 chars per line (possible unwrapped commit 
description?)

If no need to  bother with the warning, I'll change it to one line in v2.

>
> Alice



-- 
Thanks,
   Kunwu.Chan(Tao.chan)


  reply	other threads:[~2025-03-14  2:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13  8:45 [PATCH] rust: file: optimize rust symbol generation for FileDescriptorReservation Kunwu Chan
2025-03-13 10:47 ` Alice Ryhl
2025-03-14  2:33   ` Kunwu Chan [this message]
2025-03-14  9:21     ` Alice Ryhl
2025-03-17  1:26       ` Kunwu Chan

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=6c874a4f-439e-4ab2-807d-d0f59b9fe569@linux.dev \
    --to=kunwu.chan@linux.dev \
    --cc=Grace.Deng006@gmail.com \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=justinstitt@google.com \
    --cc=kunwu.chan@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.