From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Alice Ryhl <aliceryhl@google.com>
Cc: "Gary Guo" <gary@garyguo.net>, "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Nicolas Schier" <nicolas@fjasle.eu>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Tamir Duberstein" <tamird@gmail.com>,
"Christian Brauner" <brauner@kernel.org>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Dirk Behme" <dirk.behme@de.bosch.com>,
"Daniel Xu" <dxu@dxuuu.xyz>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Rob Herring (Arm)" <robh@kernel.org>,
"Matt Gilbride" <mattgilbride@google.com>,
"Paul Moore" <paul@paul-moore.com>, "Kees Cook" <kees@kernel.org>,
rust-for-linux@vger.kernel.org, llvm@lists.linux.dev,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] kbuild: rust: provide an option to inline C helpers into Rust
Date: Wed, 9 Apr 2025 22:41:14 +0200 [thread overview]
Message-ID: <CANiq72nc-A2WZn4xgfKyqr3GbgenhXjZztHqnf=12xY16ggHkg@mail.gmail.com> (raw)
In-Reply-To: <CAH5fLgifMPxer5TcWUBUYKtGsPFryqPVwXT8-5qmmY6F3=nuBw@mail.gmail.com>
On Wed, Apr 9, 2025 at 10:18 PM Alice Ryhl <aliceryhl@google.com> wrote:
>
> Is this compatible with DEBUG_INFO_BTF? I'm concerned that we have the
> same issue as in commit 5daa0c35a1f0 ("rust: Disallow BTF generation
> with Rust + LTO").
>
> The commit message should either explain why we don't have the same
> issue, or this patch should prevent configurations from enabling both.
In addition, from what we discussed in the call, it would be nice to
have some performance numbers compared to not enabling it, as well as
compared to cross-language LTO.
It would also help to know which users out there need/want to have this.
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2025-04-09 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 20:50 [PATCH v3 0/2] kbuild: rust: provide an option to inline C helpers into Rust Gary Guo
2025-03-19 20:50 ` [PATCH v3 1/2] kbuild: rust: add `CONFIG_RUSTC_CLANG_LLVM_COMPATIBLE` Gary Guo
2025-03-19 21:13 ` Tamir Duberstein
2025-03-19 20:50 ` [PATCH v3 2/2] kbuild: rust: provide an option to inline C helpers into Rust Gary Guo
2025-03-19 21:15 ` Tamir Duberstein
2025-04-09 20:17 ` Alice Ryhl
2025-04-09 20:41 ` Miguel Ojeda [this message]
2025-04-09 21:05 ` Miguel Ojeda
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='CANiq72nc-A2WZn4xgfKyqr3GbgenhXjZztHqnf=12xY16ggHkg@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.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=brauner@kernel.org \
--cc=dakr@kernel.org \
--cc=dirk.behme@de.bosch.com \
--cc=dxu@dxuuu.xyz \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=justinstitt@google.com \
--cc=kees@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=masahiroy@kernel.org \
--cc=mattgilbride@google.com \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nicolas@fjasle.eu \
--cc=ojeda@kernel.org \
--cc=paul@paul-moore.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
--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).