From: Dave Hansen <dave.hansen@intel.com>
To: Chen Yu <chen.yu@linux.dev>, Reinette Chatre <reinette.chatre@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
"Luck, Tony" <tony.luck@intel.com>,
"Chen, Yu C" <yu.c.chen@intel.com>,
"tglx@kernel.org" <tglx@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"fenghuay@nvidia.com" <fenghuay@nvidia.com>,
"babu.moger@amd.com" <babu.moger@amd.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 2/9] x86/resctrl: Require 64-bit x86 for resctrl support
Date: Mon, 24 Aug 2026 07:18:50 -0700 [thread overview]
Message-ID: <c6ab0c24-8931-4f0d-9be6-23498ab4c38b@intel.com> (raw)
In-Reply-To: <ao2UwRMgu1bGyYm9@three-body>
On 8/25/26 06:12, Chen Yu wrote:
> "32-bit x86 is maintained for legacy reasons. New CPU features are generally
> not enabled for 32-bit system, its test coverage keeps shrinking, and modern
> 32-bit distributions have become rare."
What would folks think about plopping something like the following text
in to Documentation/arch/x86/32bit-kernels.rst ?
Would that clear things up?
---
=========================================
Supporting new features on 32-bit kernels
=========================================
While it is possible to compile and run a 32-bit kernel on 64-bit
capable hardware, it is impractical and discouraged. Processors
capable of running 64-bit kernels are expected to do so.
The last 32-bit processor to come out of Intel or AMD was a Quark CPU
in 2013. Before that the most recent were some Atom CPUs in 2008.
Distros supporting 32-bit kernels and userspace are disappearing. For
example, in 2026 Ubuntu and Fedora no longer have support, with Debian
being the most notable holdout still maintaining 32-bit options.
New Processor Features
======================
When adding support for a new processor feature in 2026 and beyond it
should, by default, be:
config NEW_SNAZZY_CPU_FEATURE
depends X86_64
This ensures that the folks developing this feature do not waste
resources making it work on 32-bit kernels running on 64-bit hardware.
It is also acceptable to add this restriction to existing processor
features if 32-bit kernel support is adding maintenance burden,
especially if the feature was only ever available on 64-bit processors.
New Software Features
=====================
Let's say you are enhancing ftrace or adding a debugging feature that
has no strict dependency on processor features. It does not need to
be restricted to 64-bit only. But you might want to consider doing so
if it simplifies your implementation.
For instance, sometimes it adds complexity to support HIGHMEM. You may
add a dependency on X86_64 in cases where it is impractical or simply
challenging to support 32-bit kernels.
next prev parent reply other threads:[~2026-08-24 14:18 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 9:20 [PATCH v6 0/9] Introduce MMIO-based CMT access for Enhanced RDT Chen Yu
2026-07-25 9:22 ` [PATCH v6 1/9] x86/topology: Export topo_lookup_cpuid() for resctrl use Chen Yu
2026-08-19 22:55 ` Reinette Chatre
2026-08-22 4:16 ` Chen Yu
2026-07-25 9:22 ` [PATCH v6 2/9] x86/resctrl: Require 64-bit x86 for resctrl support Chen Yu
2026-08-19 22:55 ` Reinette Chatre
2026-08-20 15:20 ` Luck, Tony
2026-08-20 15:54 ` Reinette Chatre
2026-08-20 17:01 ` Luck, Tony
2026-08-20 17:12 ` Dave Hansen
2026-08-20 17:48 ` Reinette Chatre
2026-08-21 2:37 ` Borislav Petkov
2026-08-21 15:47 ` Reinette Chatre
2026-08-21 15:54 ` Borislav Petkov
2026-08-25 13:12 ` Chen Yu
2026-08-24 14:18 ` Dave Hansen [this message]
2026-08-24 15:15 ` Chen, Yu C
2026-08-25 2:40 ` Borislav Petkov
2026-08-21 11:28 ` Peter Zijlstra
2026-08-21 15:52 ` Borislav Petkov
2026-08-21 16:58 ` Luck, Tony
2026-08-22 0:04 ` Borislav Petkov
2026-07-25 9:22 ` [PATCH v6 3/9] x86/resctrl: Parse ACPI ERDT table and save CACD cpumask for RMDD domains Chen Yu
2026-08-19 23:01 ` Reinette Chatre
2026-08-25 8:06 ` Chen Yu
2026-08-24 15:54 ` Reinette Chatre
2026-07-25 9:23 ` [PATCH v6 4/9] x86/resctrl: Attach ACPI ERDT information to L3 mon domain on CPU online Chen Yu
2026-08-19 23:04 ` Reinette Chatre
2026-07-25 9:23 ` [PATCH v6 5/9] x86/resctrl: Parse ACPI CMRC table Chen Yu
2026-08-19 23:06 ` Reinette Chatre
2026-07-25 9:23 ` [PATCH v6 6/9] x86/resctrl: Refactor the monitor read function Chen Yu
2026-08-19 23:07 ` Reinette Chatre
2026-07-25 9:23 ` [PATCH v6 7/9] fs/resctrl: Do not invoke smp_processor_id() in preemptible context Chen Yu
2026-08-19 23:08 ` Reinette Chatre
2026-07-25 9:23 ` [PATCH v6 8/9] x86/resctrl: Introduce erdt_cpu_has() and erdt_support() Chen Yu
2026-08-19 23:08 ` Reinette Chatre
2026-07-25 9:23 ` [PATCH v6 9/9] x86/resctrl: Add MMIO-based LLC occupancy monitoring support Chen Yu
2026-08-19 23:10 ` Reinette Chatre
2026-08-13 6:43 ` [PATCH v6 0/9] Introduce MMIO-based CMT access for Enhanced RDT Chen Yu
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=c6ab0c24-8931-4f0d-9be6-23498ab4c38b@intel.com \
--to=dave.hansen@intel.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=chen.yu@linux.dev \
--cc=dave.hansen@linux.intel.com \
--cc=fenghuay@nvidia.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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
all inboxes | Powered by JetHome®