Openembedded Core Discussions
 help / color / mirror / Atom feed
From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, ross.burton@arm.com,
	mikko.rapeli@linaro.org
Subject: [PATCH 2/4] linux-yocto/6.16: cfg: x86 BIGSMP removal
Date: Wed, 10 Sep 2025 01:08:20 -0400	[thread overview]
Message-ID: <20250910050822.3273330-3-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20250910050822.3273330-1-bruce.ashfield@gmail.com>

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Integrating the following commit(s) to linux-yocto/.:

1/1 [
    Author: Bruce Ashfield
    Email: bruce.ashfield@gmail.com
    Subject: x86: drop CONFIG_BIG_SMP
    Date: Tue, 9 Sep 2025 16:07:38 -0400

    commit 0abf508675c0dbbca6a387842f90db60756c4af5
    Author: Arnd Bergmann <arnd@arndb.de>
    Date:   Wed Feb 26 22:37:06 2025 +0100

        x86/smp: Drop 32-bit "bigsmp" machine support

        The x86-32 kernel used to support multiple platforms with more than eight
        logical CPUs, from the 1999-2003 timeframe: Sequent NUMA-Q, IBM Summit,
        Unisys ES7000 and HP F8. Support for all except the latter was dropped
        back in 2014, leaving only the F8 based DL740 and DL760 G2 machines in
        this catery, with up to eight single-core Socket-603 Xeon-MP processors
        with hyperthreading.

        Like the already removed machines, the HP F8 servers at the time cost
        upwards of $100k in typical configurations, but were quickly obsoleted
        by their 64-bit Socket-604 cousins and the AMD Opteron.

        Earlier servers with up to 8 Pentium Pro or Xeon processors remain
        fully supported as they had no hyperthreading. Similarly, the more
        common 4-socket Xeon-MP machines with hyperthreading using Intel
        or ServerWorks chipsets continue to work without this, and all the
        multi-core Xeon processors also run 64-bit kernels.

        While the "bigsmp" support can also be used to run on later 64-bit
        machines (including VM guests), it seems best to discourage that
        and get any remaining users to update their kernels to 64-bit builds
        on these. As a side-effect of this, there is also no more need to
        support NUMA configurations on 32-bit x86, as all true 32-bit
        NUMA platforms are already gone.

        Signed-off-by: Arnd Bergmann <arnd@arndb.de>
        Signed-off-by: Ingo Molnar <mingo@kernel.org>
        Cc: Linus Torvalds <torvalds@linux-foundation.org>
        Link: https://lore.kernel.org/r/20250226213714.4040853-3-arnd@kernel.org

    Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
]

Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
 meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.16.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
index 76654ff516..1d44936da4 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_6.16.bb
@@ -15,7 +15,7 @@ python () {
 }
 
 SRCREV_machine ?= "c631c6cf05de829937afe048e6ae2fea15634cc8"
-SRCREV_meta ?= "29767181a0c0a97c8ba4941f6834044d9ffaed86"
+SRCREV_meta ?= "a338639c47e0a260b656415d336aaf599699d491"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.16;destsuffix=${KMETA};protocol=https"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
index c2953c5619..8764c21490 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_6.16.bb
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "29767181a0c0a97c8ba4941f6834044d9ffaed86"
+SRCREV_meta ?= "a338639c47e0a260b656415d336aaf599699d491"
 
 PV = "${LINUX_VERSION}+git"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_6.16.bb b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
index 7bafd22ef4..4bf5fa53c5 100644
--- a/meta/recipes-kernel/linux/linux-yocto_6.16.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_6.16.bb
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemux86-64 ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
 SRCREV_machine:qemumips64 ?= "2459c29bf2c3d221fd6d3222c7200b368156986e"
 SRCREV_machine ?= "01bcf423b031a36a070c7a983e45992e634fceb7"
-SRCREV_meta ?= "29767181a0c0a97c8ba4941f6834044d9ffaed86"
+SRCREV_meta ?= "a338639c47e0a260b656415d336aaf599699d491"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
 # get the <version>/base branch, which is pure upstream -stable, and the same
-- 
2.39.2



  parent reply	other threads:[~2025-09-10  5:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10  5:08 [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64 bruce.ashfield
2025-09-10  5:08 ` [PATCH 1/4] linux-yocto/6.16: cfg: DRM tweaks for guests bruce.ashfield
2025-09-10  5:08 ` bruce.ashfield [this message]
2025-09-10  5:08 ` [PATCH 3/4] yocto-bsp: introduce 6.16 bbappend bruce.ashfield
2025-09-10  5:17   ` Patchtest results for " patchtest
2025-09-10  5:08 ` [PATCH 4/4] linux-yocto/6.16: genericarm64 config bruce.ashfield
2025-09-10 11:16 ` [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64 Richard Purdie
2025-09-10 12:56   ` Bruce Ashfield
2025-09-10 12:58     ` Richard Purdie
2025-09-10 13:26 ` Mikko Rapeli
2025-09-10 13:28   ` Richard Purdie
2025-09-10 13:40     ` Mikko Rapeli

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=20250910050822.3273330-3-bruce.ashfield@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=mikko.rapeli@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.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