source large_stringclasses 2
values | subject large_stringclasses 112
values | code large_stringclasses 112
values | critique large_stringlengths 61 3.04M ⌀ | metadata dict |
|---|---|---|---|---|
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | All the MFGPLL require MFG_EB to be on for any operation on them, and
they only tick when MFG_EB is on as well, therefore making this a
parent-child relationship.
This dependency wasn't clear during the initial upstreaming of these
clock controllers, as it only made itself known when I could observe
the effects of the... | {
"author": "Nicolas Frattaroli <nicolas.frattaroli@collabora.com>",
"date": "Fri, 10 Oct 2025 22:47:13 +0200",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | Hi Nicolas,
On Fri, Oct 10, 2025 at 10:47:09PM +0200, Nicolas Frattaroli wrote:
clk_change_rate() has the following code:
if (core->flags & CLK_OPS_PARENT_ENABLE)
clk_core_prepare_enable(parent);
...
core->rate = clk_recalc(core, best_parent_rate);
...
if (core->flags &... | {
"author": "Brian Masney <bmasney@redhat.com>",
"date": "Thu, 16 Oct 2025 16:52:30 -0400",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Thursday, 16 October 2025 22:52:30 Central European Summer Time Brian Masney wrote:
I don't see how multiple prepares are a problem as long as they're
balanced.
__clk_core_init also needs special code in that case, as it calls the
bare recalc_rate op with no clk_core_enable_lock beforehand. It's also
wrong, in th... | {
"author": "Nicolas Frattaroli <nicolas.frattaroli@collabora.com>",
"date": "Fri, 17 Oct 2025 14:21:55 +0200",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | Hi Nicolas,
On Fri, Oct 17, 2025 at 02:21:55PM +0200, Nicolas Frattaroli wrote:
I agree and that makes sense. Thanks for the explanation. What you have
is a good compromise.
Reviewed-by: Brian Masney <bmasney@redhat.com> | {
"author": "Brian Masney <bmasney@redhat.com>",
"date": "Mon, 20 Oct 2025 15:36:41 -0400",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Fri, Oct 10, 2025 at 10:47:09PM +0200, Nicolas Frattaroli wrote:
I'm seeing boot regressions in -next on the Avenger96 which bisect to
this patch in -next. The board resets during startup:
[ 0.297034] /soc/display-controller@5a001000: Fixed dependency cycle(s) with /soc/bus@5c007000/i2c@5c002000/hdmi-transmitt... | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Tue, 27 Jan 2026 17:01:29 +0000",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Tue, Jan 27, 2026 at 05:01:35PM +0000, Mark Brown wrote:
I am also seeing some similar regressions even earlier on i.MX8MP
platforms, though they're resetting even earlier before any output is
produced (even with earlycon). Didn't confirm yet with a revert or
anything though. | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Tue, 27 Jan 2026 17:25:04 +0000",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Tuesday, 27 January 2026 18:25:04 Central European Standard Time Mark Brown wrote:
Someone else seemingly bisected to this commit on i.MX8MP as well
and replied to the RESEND of the series, and confirmed with a
revert[1].
I'm somewhat surprised by this, because to me it doesn't make intuitive
sense that some platf... | {
"author": "Nicolas Frattaroli <nicolas.frattaroli@collabora.com>",
"date": "Tue, 27 Jan 2026 19:18:02 +0100",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Tue, Jan 27, 2026 at 07:18:02PM +0100, Nicolas Frattaroli wrote:
Do you have a debugging patch we could run which would say which clocks
are impacted? I guess it's more of an issue for the platforms that give
no output but for at least Avenger96 I was getting earlycon output.
Please, this is making my test lab ... | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Tue, 27 Jan 2026 23:14:29 +0000",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Wednesday, 28 January 2026 00:14:29 Central European Standard Time Mark Brown wrote:
Try this one
---
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index 1b0f9d567f48..fa1443517768 100644
--- a/drivers/clk/clk.c
+++ b/drivers/clk/clk.c
@@ -1921,13 +1921,21 @@ static unsigned long clk_recalc(struct clk_core *co... | {
"author": "Nicolas Frattaroli <nicolas.frattaroli@collabora.com>",
"date": "Wed, 28 Jan 2026 15:09:46 +0100",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Wed, Jan 28, 2026 at 03:09:46PM +0100, Nicolas Frattaroli wrote:
For the Avenger96 that says:
[ 0.347816] __clk_core_init: enabling parent ck_hse for ck_per
[ 0.352230] __clk_core_init: disabling parent ck_hse for ck_per
[ 0.358207] __clk_core_init: enabling parent pll1_p for ck_mpu
[ 0.364005] __clk... | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Wed, 28 Jan 2026 14:47:08 +0000",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | Hi everyone,
Am Mittwoch, 28. Januar 2026, 15:47:08 CET schrieb Mark Brown:
This is for TQMa8MPxL/MBa8MPxL:
[ 1.452788] __clk_core_init: enabling parent audio_pll1_out for clkout1_sel
[ 1.457677] __clk_core_init: disabling parent audio_pll1_out for clkout1_sel
[ 1.464270] __clk_core_init: enabling parent au... | {
"author": "Alexander Stein <alexander.stein@ew.tq-group.com>",
"date": "Wed, 28 Jan 2026 15:55:54 +0100",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Wed, Jan 28, 2026 at 03:55:54PM +0100, Alexander Stein wrote:
As expected same result on i.MX8MP-EVK. | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Wed, 28 Jan 2026 15:21:47 +0000",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Wednesday, 28 January 2026 15:47:08 Central European Standard Time Mark Brown wrote:
Okay, on this one, there may be a problem in the clock tree.
ck_mpu is marked CLK_IS_CRITICAL, but its parent, pll1_p, is not. Clock
core doesn't seem to check whether any children of a clock are marked as
critical before disabling... | {
"author": "Nicolas Frattaroli <nicolas.frattaroli@collabora.com>",
"date": "Wed, 28 Jan 2026 17:04:55 +0100",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Wednesday, 28 January 2026 16:21:47 Central European Standard Time Mark Brown wrote:
This one puzzles me a little. arm_a53_div is neither marked critical
nor is its parent. If arm_a53_div is required for the system to function,
then I'd have expected at least it to be marked as critical, allowing us
to do the worka... | {
"author": "Nicolas Frattaroli <nicolas.frattaroli@collabora.com>",
"date": "Wed, 28 Jan 2026 17:31:35 +0100",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Wed, Jan 28, 2026 at 05:31:35PM +0100, Nicolas Frattaroli wrote:
Given that all the cores in the system are A53s I rather fear that it is
in fact critical and should be marked as such. | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Wed, 28 Jan 2026 17:08:28 +0000",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | Quoting Nicolas Frattaroli (2026-01-28 09:04:55)
Marking parents critical hasn't been strictly necessary so far because
we've been relying on the prepare/enable count on a critical child to
keep the parent prepared/enabled.
The parent may not be known yet in __clk_core_init() because we lazily
find parents. Putting ... | {
"author": "Stephen Boyd <sboyd@kernel.org>",
"date": "Wed, 28 Jan 2026 12:01:22 -0700",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Wednesday, 28 January 2026 20:01:22 Central European Standard Time Stephen Boyd wrote:
In this instance, it doesn't seem like the parent pointer is null, since
it does print a parent clock name. I think the problem really is that the
parent gets disabled before the CLK_IS_CRITICAL check re-enables it.
The issue b... | {
"author": "Nicolas Frattaroli <nicolas.frattaroli@collabora.com>",
"date": "Wed, 28 Jan 2026 20:59:24 +0100",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH v3 0/5] MediaTek PLL Refactors and Fixes | This series refactors all users of mtk-pll, just so we can enable
runtime power management for the clock controllers that want it. It's
also generally more useful to have the struct device in the pll code,
rather than the device node.
Also fix up MT8196 mfgpll to declare its parent-child relationship with
mfg_eb, and ... | On Wed, Jan 28, 2026 at 12:01:22PM -0700, Stephen Boyd wrote:
The patch is still in -next today and the issues it causes are still
visible. | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Mon, 2 Feb 2026 16:54:32 +0000",
"thread_id": "e98290b1-274a-4f8c-b629-11c1167b0370@sirena.org.uk.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Modify online_memory_block() to accept the online type through its arg
parameter rather than calling mhp_get_default_online_type() internally.
This prepares for allowing callers to specify explicit online types.
Update the caller in add_memory_resource() to pass the default online
type via a local variable.
No functi... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:34 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Enable dax kmem driver to select how to online the memory rather than
implicitly depending on the system default. This will allow users of
dax to plumb through a preferred auto-online policy for their region.
Refactor and new interface:
Add __add_memory_driver_managed() which accepts an explicit online_type
and expor... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:35 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | There is no way for drivers leveraging dax_kmem to plumb through a
preferred auto-online policy - the system default policy is forced.
Add online_type field to DAX device creation path to allow drivers
to specify an auto-online policy when using the kmem driver.
Current callers initialize online_type to mhp_get_defau... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:36 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Move the pmem region driver logic from region.c into pmem_region.c.
No functional changes.
Signed-off-by: Gregory Price <gourry@gourry.net>
---
drivers/cxl/core/Makefile | 1 +
drivers/cxl/core/core.h | 1 +
drivers/cxl/core/pmem_region.c | 191 +++++++++++++++++++++++++++++++++
drivers/cxl/core/regi... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:38 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Move the CXL DAX region device infrastructure from region.c into a
new dax_region.c file.
No functional changes.
Signed-off-by: Gregory Price <gourry@gourry.net>
---
drivers/cxl/core/Makefile | 1 +
drivers/cxl/core/core.h | 1 +
drivers/cxl/core/dax_region.c | 113 ++++++++++++++++++++++++++++++++++
d... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:39 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Add a new cxl_devdax_region driver that probes CXL regions in device
dax mode and creates dax_region devices. This allows explicit binding to
the device_dax dax driver instead of the kmem driver.
Exports to_cxl_region() to core.h so it can be used by the driver.
Signed-off-by: Gregory Price <gourry@gourry.net>
---
d... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:40 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | CXL regions may wish not to auto-configure their memory as dax kmem,
but the current plumbing defaults all cxl-created dax devices to the
kmem driver. This exposes them to hotplug policy, even if the user
intends to use the memory as a dax device.
Add plumbing to allow CXL drivers to select whether a DAX region shoul... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:37 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Explain the binding process for sysram and daxdev regions which are
explicit about which dax driver to use during region creation.
Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Gregory Price <gourry@gourry.net>
---
.../driver-api/cxl/linux/cxl-driver.rst | 43 +++++++++++++++++++
.../driver-api/cxl/linux/dax... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:42 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | In the current kmem driver binding process, the only way for users
to define hotplug policy is via a build-time option, or by not
onlining memory by default and setting each individual memory block
online after hotplug occurs. We can solve this with a configuration
step between region-probe and dax-probe.
Add the inf... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:41 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Annoyingly, my email client has been truncating my titles:
cxl: explicit DAX driver selection and hotplug policy for CXL regions
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:17:55 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, Jan 29, 2026 at 04:04:33PM -0500, Gregory Price wrote:
Looks like build regression on configs without hotplug
MMOP_ defines and mhp_get_default_online_type() undefined
Will let this version sit for a bit before spinning a v2
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Fri, 30 Jan 2026 12:34:33 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On 1/29/2026 3:04 PM, Gregory Price wrote:
This technically comes up in the devdax_region driver patch first, but I noticed it here
so this is where I'm putting it:
I like the idea here, but the implementation is all off. Firstly, devm_cxl_add_sysram_region()
is never called outside of sysram_region_driver::probe(), ... | {
"author": "\"Cheatham, Benjamin\" <benjamin.cheatham@amd.com>",
"date": "Fri, 30 Jan 2026 15:27:12 -0600",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Fri, Jan 30, 2026 at 03:27:12PM -0600, Cheatham, Benjamin wrote:
I originally tried doing with region0/region_driver, but that design
pattern is also confusing - and it creates differently bad patterns.
echo region0 > decoder0.0/create_ram_region -> creates region0
# Current pattern
echo region > dr... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Fri, 30 Jan 2026 17:12:50 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On 1/30/2026 4:12 PM, Gregory Price wrote:
Ok, that makes sense. I think I just got lost in the sauce while looking at this last
week and this explanation helped a lot.>
I think this was the source of my misunderstanding. I was trying to understand how it
works for auto regions when it's never meant to apply to them... | {
"author": "\"Cheatham, Benjamin\" <benjamin.cheatham@amd.com>",
"date": "Mon, 2 Feb 2026 11:02:37 -0600",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:34 -0500
Gregory Price <gourry@gourry.net> wrote:
Trivial comment inline. I don't really care either way.
Pushing the policy up to the caller and ensuring it's explicitly constant
for all the memory blocks (as opposed to relying on locks) seems sensible to me
even without anything else.
Rev... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:10:29 +0000",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:35 -0500
Gregory Price <gourry@gourry.net> wrote:
Hi Gregory,
I think maybe I'd have left the export for the first user outside of
memory_hotplug.c. Not particularly important however.
Maybe talk about why a caller of __add_memory_driver_managed() might want
the default? Feels like that's... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:25:24 +0000",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 11:02:37AM -0600, Cheatham, Benjamin wrote:
Auto regions explicitly use the dax_kmem path (all existing code,
unchanged)- which auto-plugs into dax/hotplug.
I do get what you're saying that everything binds on a region type,
I will look a little closer at this and see if there's something more... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 12:41:31 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 05:10:29PM +0000, Jonathan Cameron wrote:
ack. will update for next version w/ Ben's notes and the build fix.
Thanks!
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 12:46:25 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:37 -0500
Gregory Price <gourry@gourry.net> wrote:
LGTM
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com> | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:54:17 +0000",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:38 -0500
Gregory Price <gourry@gourry.net> wrote:
Needs to answer the question: Why?
Minor stuff inline.
Maybe sneak in dropping that trailing comma whilst you are moving it.
...
Bonus line... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:56:40 +0000",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:39 -0500
Gregory Price <gourry@gourry.net> wrote:
Likewise. Why? | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:57:11 +0000",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 05:25:24PM +0000, Jonathan Cameron wrote:
Less about why they want the default, more about maintaining backward
compatibility.
In the cxl driver, Ben pointed out something that made me realize we can
change `region/bind()` to actually use the new `sysram/bind` path by
just adding a one line `s... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 13:02:10 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:41 -0500
Gregory Price <gourry@gourry.net> wrote:
ZONE_MOVABLE
Trivial stuff. Will mull over this series as a whole...
My first instinctive reaction is positive - I'm just wondering
where additional drivers fit into this and whether it has the
right degree of flexibility.
This smells li... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 18:20:15 +0000",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 06:20:15PM +0000, Jonathan Cameron wrote:
I think the latter is more reasonably, MMOP_UNCONFIGURED doesn't much
make sense for memory_hotplug.c
ack.
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 13:23:37 -0500",
"thread_id": "aYDmor_ruasxaZ-7@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH v7 0/2] init/initramfs.c: make initramfs support pivot_root | From: Zhang Yunkai <zhang.yunkai@zte.com.cn>
As Luis Chamberlain suggested, I split the patch:
[init/initramfs.c: make initramfs support pivot_root]
(https://lore.kernel.org/linux-fsdevel/20210520154244.20209-1-dong.menglong@zte.com.cn/)
into three.
The goal of the series patches is to make pivot_root() support initr... | From: Zhang Yunkai <zhang.yunkai@zte.com.cn>
Introduce the function ramdisk_exec_exist, which is used to check the
exist of 'ramdisk_execute_command'.
To make path lookup follow the mount on '/', use vfs_path_lookup() in
init_eaccess(), and make the filesystem that mounted on '/' as root
during path lookup.
Reported... | {
"author": "cgel.zte@gmail.com",
"date": "Mon, 17 Jan 2022 13:43:51 +0000",
"thread_id": "20260202145234.2245271-1-safinaskar@gmail.com.mbox.gz"
} |
lkml | [PATCH v7 0/2] init/initramfs.c: make initramfs support pivot_root | From: Zhang Yunkai <zhang.yunkai@zte.com.cn>
As Luis Chamberlain suggested, I split the patch:
[init/initramfs.c: make initramfs support pivot_root]
(https://lore.kernel.org/linux-fsdevel/20210520154244.20209-1-dong.menglong@zte.com.cn/)
into three.
The goal of the series patches is to make pivot_root() support initr... | From: Zhang Yunkai <zhang.yunkai@zte.com.cn>
If using container platforms such as Docker, upon initialization it
wants to use pivot_root() so that currently mounted devices do not
propagate to containers. An example of value in this is that
a USB device connected prior to the creation of a containers on the
host gets ... | {
"author": "cgel.zte@gmail.com",
"date": "Mon, 17 Jan 2022 13:43:52 +0000",
"thread_id": "20260202145234.2245271-1-safinaskar@gmail.com.mbox.gz"
} |
lkml | [PATCH v7 0/2] init/initramfs.c: make initramfs support pivot_root | From: Zhang Yunkai <zhang.yunkai@zte.com.cn>
As Luis Chamberlain suggested, I split the patch:
[init/initramfs.c: make initramfs support pivot_root]
(https://lore.kernel.org/linux-fsdevel/20210520154244.20209-1-dong.menglong@zte.com.cn/)
into three.
The goal of the series patches is to make pivot_root() support initr... | On Mon, Jan 17, 2022 at 01:43:52PM +0000, cgel.zte@gmail.com wrote:
Sorry if this was already answered.
My understanding is that you have initramfs with docker installed on it and
with one or more container images packed there. And the desire is to use
this initramfs to run docker containers and for that you need to ... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Tue, 18 Jan 2022 09:41:02 +0200",
"thread_id": "20260202145234.2245271-1-safinaskar@gmail.com.mbox.gz"
} |
lkml | [PATCH v7 0/2] init/initramfs.c: make initramfs support pivot_root | From: Zhang Yunkai <zhang.yunkai@zte.com.cn>
As Luis Chamberlain suggested, I split the patch:
[init/initramfs.c: make initramfs support pivot_root]
(https://lore.kernel.org/linux-fsdevel/20210520154244.20209-1-dong.menglong@zte.com.cn/)
into three.
The goal of the series patches is to make pivot_root() support initr... | cgel.zte@gmail.com:
Exactly this problem solved by these two patchsets:
https://lore.kernel.org/all/20251229-work-empty-namespace-v1-0-bfb24c7b061f@kernel.org/
https://lore.kernel.org/all/20260112-work-immutable-rootfs-v2-0-88dd1c34a204@kernel.org/
--
Askar Safin | {
"author": "Askar Safin <safinaskar@gmail.com>",
"date": "Mon, 2 Feb 2026 17:52:33 +0300",
"thread_id": "20260202145234.2245271-1-safinaskar@gmail.com.mbox.gz"
} |
lkml | [PATCH 1/1] mshv: Add comment about huge page mappings in guest physical address space | From: Michael Kelley <mhklinux@outlook.com>
Huge page mappings in the guest physical address space depend on having
matching alignment of the userspace address in the parent partition and
of the guest physical address. Add a comment that captures this
information. See the link to the mailing list thread.
No code or f... | On Mon, Feb 02, 2026 at 08:51:01AM -0800, mhkelley58@gmail.com wrote:
Thanks. However, I'd suggest to reduce this commet a lot and put the
details into the commit message instead. Also, why this place? Why not a
part of the function description instead, for example?
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 2 Feb 2026 09:17:33 -0800",
"thread_id": "SN6PR02MB41570BBE17C50675E94789FDD49AA@SN6PR02MB4157.namprd02.prod.outlook.com.mbox.gz"
} |
lkml | [PATCH 1/1] mshv: Add comment about huge page mappings in guest physical address space | From: Michael Kelley <mhklinux@outlook.com>
Huge page mappings in the guest physical address space depend on having
matching alignment of the userspace address in the parent partition and
of the guest physical address. Add a comment that captures this
information. See the link to the mailing list thread.
No code or f... | From: Stanislav Kinsburskii <skinsburskii@linux.microsoft.com> Sent: Monday, February 2, 2026 9:18 AM
In general, I'm very much an advocate of putting a bit more detail into code
comments, so that someone new reading the code has a chance of figuring
out what's going on without having to search through the commit hist... | {
"author": "Michael Kelley <mhklinux@outlook.com>",
"date": "Mon, 2 Feb 2026 18:26:42 +0000",
"thread_id": "SN6PR02MB41570BBE17C50675E94789FDD49AA@SN6PR02MB4157.namprd02.prod.outlook.com.mbox.gz"
} |
lkml | [PATCH] mm/zswap: remove SWP_SYNCHRONOUS_IO swapcache bypass
workaround | From: Kairui Song <kasong@tencent.com>
Since commit f1879e8a0c60 ("mm, swap: never bypass the swap cache even
for SWP_SYNCHRONOUS_IO"), all swap-in operations go through the swap
cache, including those from SWP_SYNCHRONOUS_IO devices like
zram. Which means the workaround for swap cache bypassing
introduced by commit 2... | On Mon, Feb 2, 2026 at 1:47 AM Kairui Song <ryncsn@gmail.com> wrote:
LGTM, thanks!
Reviewed-by: Barry Song <baohua@kernel.org> | {
"author": "Barry Song <21cnbao@gmail.com>",
"date": "Mon, 2 Feb 2026 00:46:32 +0800",
"thread_id": "h334qa735tm7ejbamm4ki2zw73j2juvc4jg5xqxogcyqqvju5p@f4e73b3gqjlo.mbox.gz"
} |
lkml | [PATCH] mm/zswap: remove SWP_SYNCHRONOUS_IO swapcache bypass
workaround | From: Kairui Song <kasong@tencent.com>
Since commit f1879e8a0c60 ("mm, swap: never bypass the swap cache even
for SWP_SYNCHRONOUS_IO"), all swap-in operations go through the swap
cache, including those from SWP_SYNCHRONOUS_IO devices like
zram. Which means the workaround for swap cache bypassing
introduced by commit 2... | On Sun, Feb 1, 2026 at 9:47 AM Kairui Song <ryncsn@gmail.com> wrote:
Acked-by: Chris Li <chrisl@kernel.org>
Chris | {
"author": "Chris Li <chrisl@kernel.org>",
"date": "Mon, 2 Feb 2026 10:22:45 -0800",
"thread_id": "h334qa735tm7ejbamm4ki2zw73j2juvc4jg5xqxogcyqqvju5p@f4e73b3gqjlo.mbox.gz"
} |
lkml | [PATCH] mm/zswap: remove SWP_SYNCHRONOUS_IO swapcache bypass
workaround | From: Kairui Song <kasong@tencent.com>
Since commit f1879e8a0c60 ("mm, swap: never bypass the swap cache even
for SWP_SYNCHRONOUS_IO"), all swap-in operations go through the swap
cache, including those from SWP_SYNCHRONOUS_IO devices like
zram. Which means the workaround for swap cache bypassing
introduced by commit 2... | On Mon, Feb 02, 2026 at 01:47:32AM +0800, Kairui Song wrote:
Acked-by: Yosry Ahmed <yosry.ahmed@linux.dev>
Thanks! | {
"author": "Yosry Ahmed <yosry.ahmed@linux.dev>",
"date": "Mon, 2 Feb 2026 18:32:04 +0000",
"thread_id": "h334qa735tm7ejbamm4ki2zw73j2juvc4jg5xqxogcyqqvju5p@f4e73b3gqjlo.mbox.gz"
} |
lkml | [PATCH] iomap: handle iterator position advancing beyond current mapping | syzbot reports a WARN_ON in iomap_iter_done() when iter->pos advances
past the end of the current iomap during buffered writes.
This happens when a write completes and updates iter->pos beyond the
mapped extent before a new iomap is obtained, violating the invariant
that iter->pos must lie within the active iomap rang... | On Mon, Feb 02, 2026 at 06:30:44PM +0530, Piyush Patle wrote:
This link doesn't work. And the commit log has zero details of what's
happening either. | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Mon, 2 Feb 2026 06:48:50 -0800",
"thread_id": "aYDuI3EqwCmnc9uq@bfoster.mbox.gz"
} |
lkml | [PATCH] iomap: handle iterator position advancing beyond current mapping | syzbot reports a WARN_ON in iomap_iter_done() when iter->pos advances
past the end of the current iomap during buffered writes.
This happens when a write completes and updates iter->pos beyond the
mapped extent before a new iomap is obtained, violating the invariant
that iter->pos must lie within the active iomap rang... | On Mon, Feb 02, 2026 at 06:48:50AM -0800, Christoph Hellwig wrote:
Looks like this one:
https://syzkaller.appspot.com/bug?extid=bd5ca596a01d01bfa083
but there's no reproducer. Looks like it's through the blockdev rather
than a filesystem being involved. | {
"author": "Matthew Wilcox <willy@infradead.org>",
"date": "Mon, 2 Feb 2026 15:35:39 +0000",
"thread_id": "aYDuI3EqwCmnc9uq@bfoster.mbox.gz"
} |
lkml | [PATCH] iomap: handle iterator position advancing beyond current mapping | syzbot reports a WARN_ON in iomap_iter_done() when iter->pos advances
past the end of the current iomap during buffered writes.
This happens when a write completes and updates iter->pos beyond the
mapped extent before a new iomap is obtained, violating the invariant
that iter->pos must lie within the active iomap rang... | syzbot reports a WARN_ON in iomap_iter_done() when iter->pos advances
past the end of the current iomap during buffered writes.
This happens when a write completes and updates iter->pos beyond the
mapped extent before a new iomap is obtained, violating the invariant
that iter->pos must lie within the active iomap rang... | {
"author": "Piyush Patle <piyushpatle228@gmail.com>",
"date": "Mon, 2 Feb 2026 21:10:30 +0530",
"thread_id": "aYDuI3EqwCmnc9uq@bfoster.mbox.gz"
} |
lkml | [PATCH] iomap: handle iterator position advancing beyond current mapping | syzbot reports a WARN_ON in iomap_iter_done() when iter->pos advances
past the end of the current iomap during buffered writes.
This happens when a write completes and updates iter->pos beyond the
mapped extent before a new iomap is obtained, violating the invariant
that iter->pos must lie within the active iomap rang... | iomap_iter_done() expects that the iterator position always lies within
the current iomap range. However, during buffered writes combined with
truncate or overwrite operations, the iterator position can advance past
the end of the current iomap without the mapping being invalidated.
When this happens, iomap_iter_done... | {
"author": "Piyush Patle <piyushpatle228@gmail.com>",
"date": "Mon, 2 Feb 2026 21:14:53 +0530",
"thread_id": "aYDuI3EqwCmnc9uq@bfoster.mbox.gz"
} |
lkml | [PATCH] iomap: handle iterator position advancing beyond current mapping | syzbot reports a WARN_ON in iomap_iter_done() when iter->pos advances
past the end of the current iomap during buffered writes.
This happens when a write completes and updates iter->pos beyond the
mapped extent before a new iomap is obtained, violating the invariant
that iter->pos must lie within the active iomap rang... | On Mon, Feb 02, 2026 at 03:35:39PM +0000, Matthew Wilcox wrote:
Let's wait for a reproducer. The fix looks incorrect for anything I
could think of, so I'd rather fix a real bug. Given that lack of
reproducer I'm also not confident that it fixes anything. The fact
that the Fixes tag points to a merge commit doesn't ... | {
"author": "Christoph Hellwig <hch@infradead.org>",
"date": "Mon, 2 Feb 2026 08:05:48 -0800",
"thread_id": "aYDuI3EqwCmnc9uq@bfoster.mbox.gz"
} |
lkml | [PATCH] iomap: handle iterator position advancing beyond current mapping | syzbot reports a WARN_ON in iomap_iter_done() when iter->pos advances
past the end of the current iomap during buffered writes.
This happens when a write completes and updates iter->pos beyond the
mapped extent before a new iomap is obtained, violating the invariant
that iter->pos must lie within the active iomap rang... | On Mon, Feb 02, 2026 at 08:05:48AM -0800, Christoph Hellwig wrote:
+1 to this, FWIW. I've had that syzbot report marked in my inbox
expecting (hoping..) it would eventually spit out a reproducer to help
better characterize the cause.
This patch just appears to copy the warning check and force a lookup
cycle before we... | {
"author": "Brian Foster <bfoster@redhat.com>",
"date": "Mon, 2 Feb 2026 13:34:11 -0500",
"thread_id": "aYDuI3EqwCmnc9uq@bfoster.mbox.gz"
} |
lkml | [PATCH] arm64: dts: imx8mq: Restore VPU G2 clock to 600MHz for 4K60fps decoding | From: Ming Qian <ming.qian@oss.nxp.com>
The VPU G2 clock was reduced from 600MHz to 300MHz in commit
b27bfc5103c7 ("arm64: dts: freescale: Fix VPU G2 clock") to address
pixel errors with high-resolution HEVC postprocessor output.
However, testing shows the 300MHz clock rate is insufficient for
4K60fps decoding and th... | Am Freitag, 30. Januar 2026, 09:41:31 CET schrieb ming.qian@oss.nxp.com:
If I read the Datasheet correctly 600 MHz is only supported by overdrive
mode (also depending on the VDD_VPU).
Is this frequency really correct?
Best regards,
Alexander | {
"author": "Alexander Stein <alexander.stein@ew.tq-group.com>",
"date": "Fri, 30 Jan 2026 10:09:46 +0100",
"thread_id": "169eba79e8e1f906b1a0b59e22a531dfc7e57a1f.camel@ndufresne.ca.mbox.gz"
} |
lkml | [PATCH] arm64: dts: imx8mq: Restore VPU G2 clock to 600MHz for 4K60fps decoding | From: Ming Qian <ming.qian@oss.nxp.com>
The VPU G2 clock was reduced from 600MHz to 300MHz in commit
b27bfc5103c7 ("arm64: dts: freescale: Fix VPU G2 clock") to address
pixel errors with high-resolution HEVC postprocessor output.
However, testing shows the 300MHz clock rate is insufficient for
4K60fps decoding and th... | Hi,
Le vendredi 30 janvier 2026 à 16:41 +0800, ming.qian@oss.nxp.com a écrit :
Tested on EVK, with the downstream DCSS driver, and this change triggers DCSS
underrun (which is related to the DRAM QoS erratas on this SoC). It also
sometimes trigger the "not all macroblock decoded" warning I added recently, and
we can ... | {
"author": "Nicolas Dufresne <nicolas@ndufresne.ca>",
"date": "Fri, 30 Jan 2026 09:47:34 -0500",
"thread_id": "169eba79e8e1f906b1a0b59e22a531dfc7e57a1f.camel@ndufresne.ca.mbox.gz"
} |
lkml | [PATCH] arm64: dts: imx8mq: Restore VPU G2 clock to 600MHz for 4K60fps decoding | From: Ming Qian <ming.qian@oss.nxp.com>
The VPU G2 clock was reduced from 600MHz to 300MHz in commit
b27bfc5103c7 ("arm64: dts: freescale: Fix VPU G2 clock") to address
pixel errors with high-resolution HEVC postprocessor output.
However, testing shows the 300MHz clock rate is insufficient for
4K60fps decoding and th... | On Fri, Jan 30, 2026 at 10:09:46AM +0100, Alexander Stein wrote:
G1 and BUS clk were already set as Overdrive frequency.
This change is to only upgrading G2 from 300M to 600M.
So if your question is should we downgrade all to Nominal mode, I think
no. The freq could be override in board dts, or adding a new dts
as a... | {
"author": "Peng Fan <peng.fan@oss.nxp.com>",
"date": "Mon, 2 Feb 2026 10:41:49 +0800",
"thread_id": "169eba79e8e1f906b1a0b59e22a531dfc7e57a1f.camel@ndufresne.ca.mbox.gz"
} |
lkml | [PATCH] arm64: dts: imx8mq: Restore VPU G2 clock to 600MHz for 4K60fps decoding | From: Ming Qian <ming.qian@oss.nxp.com>
The VPU G2 clock was reduced from 600MHz to 300MHz in commit
b27bfc5103c7 ("arm64: dts: freescale: Fix VPU G2 clock") to address
pixel errors with high-resolution HEVC postprocessor output.
However, testing shows the 300MHz clock rate is insufficient for
4K60fps decoding and th... | Hi Alexander，
On 2/2/2026 10:41 AM, Peng Fan wrote:
Yes, you are right, 600MHz is the Overdriver frequency.
However, to achieve the 4K 60fps target, we set the VPU to run in
overdrive mode by default, just as Peng said.
Regards,
Ming | {
"author": "\"Ming Qian(OSS)\" <ming.qian@oss.nxp.com>",
"date": "Mon, 2 Feb 2026 13:56:47 +0800",
"thread_id": "169eba79e8e1f906b1a0b59e22a531dfc7e57a1f.camel@ndufresne.ca.mbox.gz"
} |
lkml | [PATCH] arm64: dts: imx8mq: Restore VPU G2 clock to 600MHz for 4K60fps decoding | From: Ming Qian <ming.qian@oss.nxp.com>
The VPU G2 clock was reduced from 600MHz to 300MHz in commit
b27bfc5103c7 ("arm64: dts: freescale: Fix VPU G2 clock") to address
pixel errors with high-resolution HEVC postprocessor output.
However, testing shows the 300MHz clock rate is insufficient for
4K60fps decoding and th... | Hi Nicolas,
On 1/30/2026 10:47 PM, Nicolas Dufresne wrote:
This doesn't sound like just a VPU issue; it's related to the display or
DDR.
If not displayed, do the fluster test cases yield different results at
600MHz and 300MHz?
My display is hdmi, I'll try the DCSS.
And the DDR bandwidth results measured by perf a... | {
"author": "\"Ming Qian(OSS)\" <ming.qian@oss.nxp.com>",
"date": "Mon, 2 Feb 2026 15:44:37 +0800",
"thread_id": "169eba79e8e1f906b1a0b59e22a531dfc7e57a1f.camel@ndufresne.ca.mbox.gz"
} |
lkml | [PATCH] arm64: dts: imx8mq: Restore VPU G2 clock to 600MHz for 4K60fps decoding | From: Ming Qian <ming.qian@oss.nxp.com>
The VPU G2 clock was reduced from 600MHz to 300MHz in commit
b27bfc5103c7 ("arm64: dts: freescale: Fix VPU G2 clock") to address
pixel errors with high-resolution HEVC postprocessor output.
However, testing shows the 300MHz clock rate is insufficient for
4K60fps decoding and th... | Le lundi 02 février 2026 à 15:44 +0800, Ming Qian(OSS) a écrit :
Didn't you run these tests before sending ? I can try again, but in my internal
notes, I wrote:
> Tested that, and everything becomes unstable
That was before I figure-out the IRQ handler didn't handle exception bits that
didn't stop the decoder (or ... | {
"author": "Nicolas Dufresne <nicolas@ndufresne.ca>",
"date": "Mon, 02 Feb 2026 13:44:28 -0500",
"thread_id": "169eba79e8e1f906b1a0b59e22a531dfc7e57a1f.camel@ndufresne.ca.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Change '(x - 1) + x' to '2 * (x - 1) + 1' to avoid expanding the
non-trivial __type_half_max() twice.
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
include/linux/overflow.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/l... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:18 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Since the type is always unsigned (T)-1 is always the correct value
so there is no need to use type_max().
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
include/linux/bits.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/includ... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:25 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Compile-time tests being added to BIT() make it an 'integer constant
expression' rather than a pre-processor expression for W=1 builds.
Change the BIT(PLANE_INDEX_BITS) != VIDEO_MAX_PLANES test to use
static_assert() so the code compiles.
Signed-off-by: David Laight ... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:20 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
The check for invalid 'compile time constant' parameters can easily be
changed to return 'failed' rather than generating a compile time error.
Add some tests for negative, swapped and overlarge values.
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
li... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:31 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Some compile time checks significantly bloat the pre-processor output
(particularly when the get nested).
Since the checks aren't really needed on every compilation enable with
W=c (adds -DKBUILD_EXTRA_WARNc) so the checks can be enabled per-build.
Make W=1 imply W=c s... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:19 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Compile-time tests being added to BIT() make it an 'integer constant
expression' rather than a pre-processor expression for W=1 builds.
Change the FRAC_ACC != BDS_UNIT test to use static_assert() so the code
compiles.
Signed-off-by: David Laight <david.laight.linux@g... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:21 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
asm/tlb.h isn't part of the vdso, use the linux/bits.h header.
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
arch/x86/include/asm/tlb.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/tlb.h b/arch/x86/include/... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:24 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Casting the value of BIT_U*() and GENMASK_U8() to (u8) is pointless.
Although it changes what typeof(BIT_U8()) returns the value will
always be promoted to 'signed int' before it is used.
Instead force the expression to be an unsigned type.
Avoids unexpected sign exte... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:26 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
thread_info_tif.h isn't part of the vdso, use the linux/bits.h header.
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
include/asm-generic/thread_info_tif.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/asm-generic/thread_... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:23 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
The assembler only supports one type of signed integers, so expressions
using BITS_PER_LONG (etc) cannot be guaranteed to be correct.
Use ((2 << (h)) - (1 << (l))) for all assembler GENMASK() expansions and
add definitions of BIT_Uxx() as (1 << (nr)).
Note that 64bit... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:27 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Compile-time tests being added to BIT() make it an 'integer constant
expression' rather than a pre-processor expression for W=1 builds.
This means BIT() can't be used in pre-processor conditional that
checks 'PAGE_SIZE > IXGBE_MAX_DATA_PER_TXD'.
Change to use a normal... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:22 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
The current checks in GENMASK/BIT (eg reversed high/low) only work
for 'integer constant expressions' not 'compile-time constants'.
This is true for const_true() and -Wshift-count-overflow/negative.
While compile-time constants may be unusual, they can happen through
f... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:28 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Since all the GENMASK() values are compile-time constants they can
be tested with BUILD_BUG_ON() rather than KUNIT_EXPECT_EQ().
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
lib/tests/test_bits.c | 90 +++++++++++++++++++++----------------------
1 fi... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:30 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
The definition of BIT() was moved from linux/bits.h to vdso/bits.h to
isolate the vdso from 'normal' kernel headers.
BIT_ULL() was then moved to be defined in the same place for consistency.
Since then linux/bits.h had gained BIT_Unn() and it really makes sense
for BI... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:29 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, Jan 21, 2026 at 02:57:29PM +0000, david.laight.linux@gmail.com wrote:
This is ugly.
Why can't the vDSO code make use of those checks, too?
Or use _BITUL() from the UAPI in the vDSO and remove vdso/bits.h. | {
"author": "Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <thomas.weissschuh@linutronix.de>",
"date": "Wed, 21 Jan 2026 16:17:18 +0100",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On 21/01/2026 at 15:57, david.laight.linux@gmail.com wrote:
Did those new checks actually found any real problem in the code? This
adds a lot of complexity so I am not sure whether this is a winning
trade-off.
But then, you only solve that shift problem for GENMASK() and
BIT(). Any other usage of the left/right shif... | {
"author": "Vincent Mailhol <mailhol@kernel.org>",
"date": "Wed, 21 Jan 2026 19:43:07 +0100",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, 21 Jan 2026 19:43:07 +0100
Vincent Mailhol <mailhol@kernel.org> wrote:
Not in an x86-64 allmodconfig build.
They might in a 32bit one where there have definitely been issues.
I suspect the compiler test will find more than sparse.
I liked getting that to work, but maybe it is OTT.
But the W=c is more gener... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Wed, 21 Jan 2026 19:14:48 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, 21 Jan 2026 16:17:18 +0100
Thomas Weißschuh <thomas.weissschuh@linutronix.de> wrote:
It works :-)
I could have put an #ifndef BIT in vdso/bits.h instead.
I didn't actually find anything that just needed vdso/bits.h
linux/bits.h would get included - eg (IIRC) because of warn_on_once().
I'm not that sure why... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Wed, 21 Jan 2026 19:24:51 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, Jan 21, 2026 at 02:57:18PM +0000, david.laight.linux@gmail.com wrote:
Sure!
Reviewed-by: Kees Cook <kees@kernel.org>
--
Kees Cook | {
"author": "Kees Cook <kees@kernel.org>",
"date": "Wed, 21 Jan 2026 12:59:36 -0800",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20260120]
url: https://github.com/intel-lab-lkp/linux/commits/david-laight-linux-gmail-com/overflow-Reduce-expansion-of-__type_max/20260122-013456
base: next-20260120
patch link: https://lore.kernel.org/r/20260121145731.... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 22 Jan 2026 08:50:22 +0800",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20260120]
url: https://github.com/intel-lab-lkp/linux/commits/david-laight-linux-gmail-com/overflow-Reduce-expansion-of-__type_max/20260122-013456
base: next-20260120
patch link: https://lore.kernel.org/r/20260121145731.... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 22 Jan 2026 09:11:53 +0800",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20260120]
url: https://github.com/intel-lab-lkp/linux/commits/david-laight-linux-gmail-com/overflow-Reduce-expansion-of-__type_max/20260122-013456
base: next-20260120
patch link: https://lore.kernel.org/r/20260121145731.... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 22 Jan 2026 09:23:16 +0800",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on next-20260120]
url: https://github.com/intel-lab-lkp/linux/commits/david-laight-linux-gmail-com/overflow-Reduce-expansion-of-__type_max/20260122-013456
base: next-20260120
patch link: https://lore.kernel.org/r/20260121145... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 22 Jan 2026 12:41:22 +0800",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Wed, Jan 21, 2026 at 07:24:51PM +0000, David Laight wrote:
The #ifndef in vdso/bits.h is not much better IMO.
Given that there a multiple nicer options why not use on of those?
That is a bug. The vdso code should only include the vdso/ namespace.
Right now the inclusions are all over the place. I'd like to clean ... | {
"author": "Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <thomas.weissschuh@linutronix.de>",
"date": "Thu, 22 Jan 2026 08:39:42 +0100",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 09:11:53 +0800
kernel test robot <lkp@intel.com> wrote:
...
This might be a real bug.
The bit of mm.h is:
#define PP_DMA_INDEX_SHIFT (1 + __fls(PP_SIGNATURE - POISON_POINTER_DELTA))
#if POISON_POINTER_DELTA > 0
/* PP_SIGNATURE includes POISON_POINTER_DELTA, so limit the size of the DMA
* index ... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 10:25:54 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 09:23:16 +0800
kernel test robot <lkp@intel.com> wrote:
...
Unless I change BIT() back I'll change that to a static_assert().
David | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 10:30:29 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 12:41:22 +0800
kernel test robot <lkp@intel.com> wrote:
Can we stop sparse complaining about sizeof(VLA) ?
David | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 10:33:37 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, Jan 22, 2026 at 10:33:37AM +0000, David Laight wrote:
First of all, the LKP should install the fork of sparse by Al Viro. That will
fix tons of warnings that are related to modules and speed up the process
itself.
--
With Best Regards,
Andy Shevchenko | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Thu, 22 Jan 2026 16:26:44 +0200",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 16:26:44 +0200
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
The problem I have is I want to generate a compile time error inside:
__builtin_choose_expr(__is_constexpr(x), x && error_a(),
statically_true(y) && error_b());
Neither static_assert() nor a negative bitfield can be used ... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 14:55:56 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, 22 Jan 2026 10:25:54 +0000
David Laight <david.laight.linux@gmail.com> wrote:
I've managed to do an s390 cross build.
It is all quite obvious really.
For s390 PAGE_OFFSET is usually zero (I think kernel and user mappings are separate?).
This make PP_DMA_INDEX_BITS 0.
PP_SIGNATURE is 64 - so PP_DMA_INDEX_SHIFT... | {
"author": "David Laight <david.laight.linux@gmail.com>",
"date": "Thu, 22 Jan 2026 20:10:20 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, Jan 22, 2026 at 10:33:37AM +0000, David Laight wrote:
Got it, we will avoid the direct report this 'sparse: Variable length array is used' warning. | {
"author": "Philip Li <philip.li@intel.com>",
"date": "Fri, 23 Jan 2026 09:24:50 +0800",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Thu, Jan 22, 2026 at 04:26:44PM +0200, Andy Shevchenko wrote:
Thanks Andy, i will switch to the repo from Al Viro for sparse. | {
"author": "Philip Li <philip.li@intel.com>",
"date": "Fri, 23 Jan 2026 09:25:36 +0800",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | Adding the relevant parties to the discussion:
+To: Al Viro
+To: Chris Li
On 23/01/2026 at 02:25, Philip Li wrote:
Al Viro's fork just adds 8 commit on top of the upstream sparse repo.
Wouldn't it be possible to just merge those?
That would be much less confusing.
Yours sincerely,
Vincent Mailhol | {
"author": "Vincent Mailhol <mailhol@kernel.org>",
"date": "Fri, 23 Jan 2026 09:01:04 +0100",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Fri, Jan 23, 2026 at 09:01:04AM +0100, Vincent Mailhol wrote:
Ideally yes, but you also should kick the distro's asses to update it, and
the sparse should bump its version...
Seems Al become a sparse maintainer de facto :-)
--
With Best Regards,
Andy Shevchenko | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Fri, 23 Jan 2026 10:11:19 +0200",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Fri, Jan 23, 2026 at 10:11:19AM +0200, Andy Shevchenko wrote:
Huh? What happened to Chris? FWIW, I do have some followups to that series
sitting locally; need to get that finished (mostly for proper __VA_OPT__
handling; that got stalled on the lovely corner cases where the interplay
with side effects of macro ex... | {
"author": "Al Viro <viro@zeniv.linux.org.uk>",
"date": "Fri, 23 Jan 2026 08:20:27 +0000",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On Fri, Jan 23, 2026 at 08:20:27AM +0000, Al Viro wrote:
I don't know, but upstream sparse haven't applied any solution for
MODULE*("FOO") stuff, nor reaction on my ping in that discussion
(I did it like week or so ago).
Thanks for doing all this!
--
With Best Regards,
Andy Shevchenko | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Fri, 23 Jan 2026 10:24:01 +0200",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | On 23/01/2026 at 09:24, Andy Shevchenko wrote:
After the project hiatus, I can imagine that there is some confusion :)
But Chris is back in his role of maintainer since September 2025. See:
- https://lore.kernel.org/linux-sparse/CACePvbXDO1ZybDu3RaFhED9D-9gC6LTMpWrxoh5xD+ZO5SLdzA@mail.gmail.com/
- https://git.ke... | {
"author": "Vincent Mailhol <mailhol@kernel.org>",
"date": "Fri, 23 Jan 2026 09:32:39 +0100",
"thread_id": "aYDt8gLSRbFHwVpn@yury.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.