From: Michael Ellerman <mpe@ellerman.id.au> To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> Cc: rust-for-linux@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-kernel <linux-kernel@vger.kernel.org> Subject: Re: [PATCH 0/4] Rust for Linux for ppc64le Date: Tue, 23 Mar 2021 23:15:50 +1100 [thread overview] Message-ID: <87mtuugj61.fsf@mpe.ellerman.id.au> (raw) In-Reply-To: <CANiq72n-tMww2U+eQ=iHOh5u1JQgjM0b1E3XQ9jpWMfpdQ5+=g@mail.gmail.com> Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> writes: > Hi Michael, > > On Tue, Mar 23, 2021 at 4:27 AM Michael Ellerman <mpe@ellerman.id.au> wrote: >> >> Hi all, >> >> Here's a first attempt at getting the kernel Rust support building on powerpc. > > Thanks a *lot*! It is great to have more architectures rolling. No worries. >> It's powerpc64le only for now, as that's what I can easily test given the >> distros I have installed. Though powerpc and powerpc64 are also Tier 2 platforms > > Even if it is just 64-bit, it is very good to have it! > >> so in theory should work. Supporting those would require something more >> complicated than just pointing rustc at arch/$(ARCH)/rust/target.json. > > Yeah, the arch/$(ARCH)/rust/target.json dance is a placeholder -- I > need to figure out how to do that more cleanly, likely generating them > on the fly. Yeah that's a good idea. That way they can be made to exactly match the kernel configuration. >> This is based on 832575d934a2 from the Rust-for-Linux tree. Anything newer gives >> me errors about symbol name lengths. I figured I'd send this anyway, as it seems >> like those errors are probably not powerpc specific. > > Sure, feel free to send things even if they don't work completely. > > I will take a look at the symbol name lengths -- I increased that > limit to 512 and added support for 2-byte lengths in the tables, but > perhaps something is missing. If I manage to make it work, I can add > ppc64le to our CI! :-) It would be nice to be in the CI. I was building natively so I haven't tried cross compiling yet (which we'll need for CI). >> Michael Ellerman (4): >> rust: Export symbols in initialized data section >> rust: Add powerpc64 as a 64-bit target_arch in c_types.rs >> powerpc/rust: Add target.json for ppc64le >> rust: Enable for ppc64le > > Regarding the development process: at least until the RFC we are > working with the usual GitHub PR workflow (for several reasons: having > a quick CI setup, getting new Rust developers on-board, having a list > of "issues", cross-reference with the Rust repo, etc.). > > I can take patches from the list, of course, but since we are pre-RFC, > do you mind if they get rebased etc. through there? No I don't mind at all. I just sent patches so other ppc folks could see what I had, and it's kind of the process I'm used to. I can send a pull request if that's easiest. cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au> To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel <linux-kernel@vger.kernel.org>, rust-for-linux@vger.kernel.org Subject: Re: [PATCH 0/4] Rust for Linux for ppc64le Date: Tue, 23 Mar 2021 23:15:50 +1100 [thread overview] Message-ID: <87mtuugj61.fsf@mpe.ellerman.id.au> (raw) In-Reply-To: <CANiq72n-tMww2U+eQ=iHOh5u1JQgjM0b1E3XQ9jpWMfpdQ5+=g@mail.gmail.com> Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> writes: > Hi Michael, > > On Tue, Mar 23, 2021 at 4:27 AM Michael Ellerman <mpe@ellerman.id.au> wrote: >> >> Hi all, >> >> Here's a first attempt at getting the kernel Rust support building on powerpc. > > Thanks a *lot*! It is great to have more architectures rolling. No worries. >> It's powerpc64le only for now, as that's what I can easily test given the >> distros I have installed. Though powerpc and powerpc64 are also Tier 2 platforms > > Even if it is just 64-bit, it is very good to have it! > >> so in theory should work. Supporting those would require something more >> complicated than just pointing rustc at arch/$(ARCH)/rust/target.json. > > Yeah, the arch/$(ARCH)/rust/target.json dance is a placeholder -- I > need to figure out how to do that more cleanly, likely generating them > on the fly. Yeah that's a good idea. That way they can be made to exactly match the kernel configuration. >> This is based on 832575d934a2 from the Rust-for-Linux tree. Anything newer gives >> me errors about symbol name lengths. I figured I'd send this anyway, as it seems >> like those errors are probably not powerpc specific. > > Sure, feel free to send things even if they don't work completely. > > I will take a look at the symbol name lengths -- I increased that > limit to 512 and added support for 2-byte lengths in the tables, but > perhaps something is missing. If I manage to make it work, I can add > ppc64le to our CI! :-) It would be nice to be in the CI. I was building natively so I haven't tried cross compiling yet (which we'll need for CI). >> Michael Ellerman (4): >> rust: Export symbols in initialized data section >> rust: Add powerpc64 as a 64-bit target_arch in c_types.rs >> powerpc/rust: Add target.json for ppc64le >> rust: Enable for ppc64le > > Regarding the development process: at least until the RFC we are > working with the usual GitHub PR workflow (for several reasons: having > a quick CI setup, getting new Rust developers on-board, having a list > of "issues", cross-reference with the Rust repo, etc.). > > I can take patches from the list, of course, but since we are pre-RFC, > do you mind if they get rebased etc. through there? No I don't mind at all. I just sent patches so other ppc folks could see what I had, and it's kind of the process I'm used to. I can send a pull request if that's easiest. cheers
next prev parent reply other threads:[~2021-03-23 12:16 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 3:26 [PATCH 0/4] Rust for Linux for ppc64le Michael Ellerman 2021-03-23 3:26 ` [PATCH 1/4] rust: Export symbols in initialized data section Michael Ellerman 2021-03-23 3:26 ` [PATCH 2/4] rust: Add powerpc64 as a 64-bit target_arch in c_types.rs Michael Ellerman 2021-03-23 3:26 ` [PATCH 3/4] powerpc/rust: Add target.json for ppc64le Michael Ellerman 2021-03-23 9:28 ` Miguel Ojeda 2021-03-23 9:28 ` Miguel Ojeda 2021-03-23 3:26 ` [PATCH 4/4] rust: Enable " Michael Ellerman 2021-03-23 10:02 ` [PATCH 0/4] Rust for Linux " Miguel Ojeda 2021-03-23 10:02 ` Miguel Ojeda 2021-03-23 12:15 ` Michael Ellerman [this message] 2021-03-23 12:15 ` Michael Ellerman 2021-03-23 14:26 ` Miguel Ojeda 2021-03-23 14:26 ` 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=87mtuugj61.fsf@mpe.ellerman.id.au \ --to=mpe@ellerman.id.au \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=miguel.ojeda.sandonis@gmail.com \ --cc=rust-for-linux@vger.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: linkBe 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.