From: Harish Sadineni <Harish.Sadineni@windriver.com>
To: yoann.congal@smile.fr, mathieu.dubois-briand@bootlin.com
Cc: Hemanth.KumarMD@windriver.com,
openembedded-core@lists.openembedded.org,
Sundeep.Kokkonda@windriver.com, "MacLeod,
Randy" <Randy.MacLeod@windriver.com>
Subject: Re: [OE-core] [PATCH] rust: Upgrade 1.92.0 -> 1.93.0
Date: Mon, 2 Feb 2026 21:21:33 +0530 [thread overview]
Message-ID: <89c2464f-8fa3-4be4-83e6-c14b9b310990@windriver.com> (raw)
In-Reply-To: <CAMSfU+5-gHPYDLsxKjSK-BRVqhZ+dis+b1hE+82LAL0pAQL7CA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6125 bytes --]
On 2/2/2026 8:45 PM, Yoann Congal via lists.openembedded.org wrote:
> **
> *CAUTION: This email comes from a non Wind River email account!*
> Do not click links or open attachments unless you recognize the sender
> and know the content is safe.
>
>
> Le dim. 1 févr. 2026 à 08:52, Mathieu Dubois-Briand via
> lists.openembedded.org <http://lists.openembedded.org>
> <mathieu.dubois-briand=bootlin.com@lists.openembedded.org> a écrit :
>
> On Fri Jan 30, 2026 at 2:41 PM CET, Hemanth.KumarMD via
> lists.openembedded.org <http://lists.openembedded.org> wrote:
> > From: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
> >
> > https://blog.rust-lang.org/2026/01/22/Rust-1.93.0/
> > Rust changes: https://github.com/rust-lang/rust/releases/tag/1.93.0
> > Cargo changes:
> https://doc.rust-lang.org/nightly/cargo/CHANGELOG.html#cargo-193-2026-01-22
> >
> > * rust-oe-selftest.patch updated for 1.93:
> > Renamed UI test directive from add-core-stubs to add-minicore
> as in
> >
> https://github.com/rust-lang/rust/commit/3796f7de57f5d4cf4325d1f13aeb07fdaa57983b
> >
> > * OE-selftests:
> > - Exclude src/tools/remote-test-client from test suite.
> > This unit test modifies the TEST_DEVICE_ADDR environment
> variable,
> > which breaks the OE test harness that uses the same variable for
> > QEMU remote testing. Filed a bug with upstream:
> > https://github.com/rust-lang/rust/issues/151823
> >
> > - Enable +v8a feature for cortexa57.
> > Rust 1.93.0 added a regression test (PR #149549) to verify
> that the
> > ARMv8-A system register ttbr0_el2 is recognized in inline
> assembly.
> > This addresses issue #97724 where LLVM wasn't recognizing
> ttbr0_el2
> > as a valid register. Upstream Rust enables +v8a by default
> for all
> > AArch64 targets (PR #105026), but Yocto's custom target
> specification
> > doesn't inherit this. Adding +v8a ensures LLVM recognizes
> ARMv8-A
> > system registers, fixing the test failure.
> >
> > Related upstream links:
> > - PR #149549: https://github.com/rust-lang/rust/pull/149549
> > - Issue #97724: https://github.com/rust-lang/rust/issues/97724
> > - PR #105026: https://github.com/rust-lang/rust/pull/105026
> >
> > Test results:
> >
> > rust v1.93.0
> > +-------------+--------+---------+
> > | Machine | Passed | Skipped |
> > +-------------+--------+---------+
> > | qemux86-64 | 21,689 | 646 |
> > | qemux86 | 21,439 | 896 |
> > | qemuarm64 | 21,495 | 840 |
> > | qemuarm | 21,421 | 914 |
> > | qemuriscv64 | 21,466 | 869 |
> > +-------------+--------+---------+
> >
> > Test results difference (1.93.0 - 1.92.0):
> >
> > +-------------+--------+---------+
> > | Machine | Passed | Skipped |
> > +-------------+--------+---------+
> > | qemux86-64 | +205 | +33 |
> > | qemux86 | +205 | +33 |
> > | qemuarm64 | +206 | +32 |
> > | qemuarm | +205 | +33 |
> > | qemuriscv64 | +205 | +33 |
> > +-------------+--------+---------+
> >
> > Signed-off-by: Hemanth Kumar M D <Hemanth.KumarMD@windriver.com>
> > ---
>
> Hi Hemanth,
>
> Thanks for the upgrade.
>
> I suspect this is responsible of the
> runtime_test.RustKernel.test_kernel_rust_sample selftest failure:
>
> 2026-01-31 16:20:41,991 - oe-selftest - INFO -
> runtime_test.RustKernel.test_kernel_rust_sample
> (subunit.RemotedTestCase)
> 2026-01-31 16:20:41,994 - oe-selftest - INFO - ... FAIL
> ...
> ERROR: linux-yocto-6.16.11+git-r0 do_compile: Execution of
> '/srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-766138/tmp/work/qemux86_64-poky-linux/linux-yocto/6.16.11+git/temp/run.do_compile.189616'
> failed with exit code 1
> ...
> | error: unknown unstable option: `no-jump-tables`
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3127
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3022
>
> Can you have a look at what is going wrong here?
>
>
> Hello,
>
> To clarify because this is not totally obvious:
> This test is defined in the "[PATCH v5 00/15] Enable rust support for
> linux kernel" from Harish.Sadineni (also at Windriver)
> https://lore.kernel.org/openembedded-core/20260129163910.2612040-10-Harish.Sadineni@windriver.com/
> So, the test is not present on master (or even master-next).
Hi all,
"[PATCH v5 00/15] Enable rust support for linux kernel" this series is
taken to mathieu/msater-next, on top of this series when testing with
rust-1.93.0 patch
has caused this build failure.
This failure is already identified in upstream and has a fix in
linux-kernel 6.18/master, so i will send a backport fix to linux-yocto
v6.16.
https://github.com/torvalds/linux/commit/789521b4717fd6bd85164ba5c131f621a79c9736
Can the rust 1.93.0 patch be tested/merged , By the time above mentioned
backported patch taken to linux-yocto v6.16?.
>
>
> Thanks,
> Mathieu
>
> --
> Mathieu Dubois-Briand, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
>
>
>
>
> --
> Yoann Congal
> Smile ECS
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#230373):https://lists.openembedded.org/g/openembedded-core/message/230373
> Mute This Topic:https://lists.openembedded.org/mt/117544255/8054390
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [Harish.Sadineni@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
[-- Attachment #2: Type: text/html, Size: 13658 bytes --]
next prev parent reply other threads:[~2026-02-02 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 13:41 [PATCH] rust: Upgrade 1.92.0 -> 1.93.0 Hemanth.KumarMD
2026-01-30 18:14 ` [OE-core] " Randy MacLeod
2026-02-01 7:51 ` Mathieu Dubois-Briand
2026-02-02 15:15 ` Yoann Congal
2026-02-02 15:51 ` Harish Sadineni [this message]
2026-02-02 15:38 ` Harish Sadineni
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=89c2464f-8fa3-4be4-83e6-c14b9b310990@windriver.com \
--to=harish.sadineni@windriver.com \
--cc=Hemanth.KumarMD@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=yoann.congal@smile.fr \
/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