From: Conor Dooley <conor@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Ramon de C Valle" <rcvalle@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Conor Dooley" <conor.dooley@microchip.com>,
linux-riscv@lists.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>,
"Jonathan Corbet" <corbet@lwn.net>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Tom Rix" <trix@redhat.com>,
rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
"Matthew Maurer" <mmaurer@google.com>,
"Sami Tolvanen" <samitolvanen@google.com>
Subject: Re: [PATCH v1 0/2] RISC-V: enable rust
Date: Mon, 12 Feb 2024 20:17:31 +0000 [thread overview]
Message-ID: <20240212-demotion-blitz-1c9ab85dbc73@spud> (raw)
In-Reply-To: <CANiq72=VBFvB9O9c84YxpBBftpfNnnXx-+Xes0h8h6rN3EN5pA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On Mon, Feb 12, 2024 at 08:11:21PM +0100, Miguel Ojeda wrote:
> On Mon, Feb 12, 2024 at 8:02 PM Ramon de C Valle <rcvalle@google.com> wrote:
> >
> > Sorry for the late reply. Sami might be the best person to answer this, but KCFI (not CFI) tests are lowered by passes that are architecture specific (see https://reviews.llvm.org/D119296), so we'd need to add support for RISC-V. There is no additional work required in the Rust compiler besides enabling it for the new target.
>
> Thanks a lot Ramon!
>
> Then for RISC-V let's go for the `depends on` for the moment, and we
> can remove when the support lands for RISC-V (ideally when someone has
> managed to boot it at least under some configuration).
If all you want is a boot under some configuration, that's not
difficult. After all, I found the original issue by booting a kernel
with CFI_CLANG enabled on the C side...
> There is no additional work required in the Rust compiler besides enabling it for the new target.
This is not super clear though, it says "in the Rust compiler", not "in
the kernel's buildsystem".
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-02-12 20:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 10:24 [PATCH v1 0/2] RISC-V: enable rust Conor Dooley
2023-03-07 10:24 ` [PATCH v1 1/2] scripts: generate_rust_target: enable building on RISC-V Conor Dooley
2023-03-07 11:21 ` Miguel Ojeda
2023-03-07 10:24 ` [PATCH v1 2/2] RISC-V: enable building 64-bit kernels with rust support Conor Dooley
2023-03-07 10:56 ` Miguel Ojeda
2023-03-07 11:01 ` Conor Dooley
2023-03-07 11:56 ` Miguel Ojeda
2023-03-07 12:51 ` Conor Dooley
2023-03-07 11:07 ` [PATCH v1 0/2] RISC-V: enable rust Miguel Ojeda
2023-03-30 8:23 ` Conor Dooley
2023-03-30 9:11 ` Conor Dooley
2023-04-03 16:35 ` Miguel Ojeda
2023-04-03 17:14 ` Conor Dooley
2023-04-05 21:18 ` Conor Dooley
2023-04-03 16:32 ` Miguel Ojeda
2023-06-08 7:01 ` Conor Dooley
2023-06-08 7:10 ` Conor Dooley
2023-06-08 7:50 ` Kwanghoon Son
2023-06-08 11:52 ` Miguel Ojeda
2023-06-08 12:28 ` Conor Dooley
2024-01-17 11:30 ` Conor Dooley
2024-01-17 18:23 ` Miguel Ojeda
2024-01-18 15:49 ` Conor Dooley
2024-01-18 16:09 ` Miguel Ojeda
2024-01-25 12:30 ` Conor Dooley
2024-01-25 12:50 ` Miguel Ojeda
2024-01-25 13:45 ` Conor Dooley
2024-01-26 21:00 ` Miguel Ojeda
2024-01-26 22:00 ` Conor Dooley
2024-01-27 13:46 ` Miguel Ojeda
2024-02-09 15:18 ` Conor Dooley
2024-02-10 8:13 ` Trevor Gross
2024-02-12 19:03 ` Ramon de C Valle
2024-02-12 20:36 ` Sami Tolvanen
2024-02-13 20:08 ` Ramon de C Valle
2024-02-14 3:14 ` Trevor Gross
[not found] ` <CAOcBZORDaHHH3jTL3GO7OsDubhhyQE0Uy2uAjJpiRzrKBgqaOw@mail.gmail.com>
2024-02-12 19:11 ` Miguel Ojeda
2024-02-12 20:17 ` Conor Dooley [this message]
2024-02-12 20:37 ` Conor Dooley
2024-02-13 20:09 ` Ramon de C Valle
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=20240212-demotion-blitz-1c9ab85dbc73@spud \
--to=conor@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mmaurer@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rcvalle@google.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=tmgross@umich.edu \
--cc=trix@redhat.com \
--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).