From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
"Mukesh Kumar Chaurasiya (IBM)" <mkchauras@gmail.com>
Cc: linkmauve@linkmauve.fr, ojeda@kernel.org, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, corbet@lwn.net, maddy@linux.ibm.com,
mpe@ellerman.id.au, npiggin@gmail.com, peterz@infradead.org,
jpoimboe@kernel.org, jbaron@akamai.com, rostedt@goodmis.org,
ardb@kernel.org, rust-for-linux@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V4 2/3] rust: Add PowerPC support
Date: Mon, 9 Feb 2026 13:29:22 +0100 [thread overview]
Message-ID: <b07f1bc6-c63e-4b97-95d6-c639186a89dd@kernel.org> (raw)
In-Reply-To: <CANiq72nqH=H4a_Yo17KPmku5pPRMVRBADgj8j+=TcR=3r0vOdQ@mail.gmail.com>
Le 09/02/2026 à 13:02, Miguel Ojeda a écrit :
> On Mon, Feb 9, 2026 at 11:55 AM Mukesh Kumar Chaurasiya (IBM)
> <mkchauras@gmail.com> wrote:
>>
>> These changes aren’t the only ones required to get the kernel to compile
>> and link on PowerPC
>
> Is this patch not complete, then? It is up to the PowerPC maintainers
> what they want to merge, of course, but I don't think we should add
> the line in `Documentation/` if it does not work yet.
As far as I understand the patch is complete, the problem is outside the
kernel, it is in the libcore provided by rust or the rust compiler.
That libcore seems to call __udivdi3() and __umoddi3() which are not
provided by the kernel. Instead if should call the functions do_div()
and friends provided by include/asm-generic/div64.h, or provide
__udivdi3() and __umoddi3() on its own.
Christophe
next prev parent reply other threads:[~2026-02-09 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 10:54 [PATCH V4 0/3] Rust support for powerpc Mukesh Kumar Chaurasiya (IBM)
2026-02-09 10:54 ` [PATCH V4 1/3] powerpc/jump_label: adjust inline asm to be consistent Mukesh Kumar Chaurasiya (IBM)
2026-02-09 10:54 ` [PATCH V4 2/3] rust: Add PowerPC support Mukesh Kumar Chaurasiya (IBM)
2026-02-09 12:02 ` Miguel Ojeda
2026-02-09 12:29 ` Christophe Leroy (CS GROUP) [this message]
2026-02-09 12:48 ` Miguel Ojeda
2026-02-10 5:27 ` Mukesh Kumar Chaurasiya
2026-02-10 9:17 ` Miguel Ojeda
2026-02-10 9:42 ` Link Mauve
2026-02-10 9:53 ` Miguel Ojeda
2026-02-10 5:11 ` kernel test robot
2026-02-09 10:54 ` [PATCH V4 3/3] powerpc: Enable Rust for ppc64le Mukesh Kumar Chaurasiya (IBM)
2026-02-09 11:52 ` Miguel Ojeda
2026-02-10 5:29 ` Mukesh Kumar Chaurasiya
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=b07f1bc6-c63e-4b97-95d6-c639186a89dd@kernel.org \
--to=chleroy@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=ardb@kernel.org \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=linkmauve@linkmauve.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lossin@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mkchauras@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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