data_type large_stringclasses 3
values | source large_stringclasses 29
values | code large_stringlengths 98 49.4M | filepath large_stringlengths 5 161 ⌀ | message large_stringclasses 234
values | commit large_stringclasses 234
values | subject large_stringclasses 418
values | critique large_stringlengths 101 1.26M ⌀ | metadata dict |
|---|---|---|---|---|---|---|---|---|
lkml_critique | lkml | Hi,
Some endpoint platforms cannot use a GIC ITS-backed MSI domain for
EP-side doorbells. In those cases, endpoint function (EPF) drivers
cannot provide a doorbell to the root complex (RC), and features such as
vNTB may fall back to polling with significantly higher latency.
This series adds an alternate doorbell bac... | null | null | null | [PATCH v9 0/7] PCI: endpoint: pci-ep-msi: Add embedded doorbell fallback | On Fri, Feb 20, 2026 at 11:27:05AM +0100, Niklas Cassel wrote:
Niklas, agreed, I had the same thought (ie. bind-time check could be
sufficient). Thanks for the follow-up.
Alok, thanks for picking it up.
Best regards,
Koichiro | {
"author": "Koichiro Den <den@valinux.co.jp>",
"date": "Sat, 21 Feb 2026 02:53:17 +0900",
"is_openbsd": false,
"thread_id": "aaG5asXVV5sxRbnQ@ryzen.mbox.gz"
} |
lkml_critique | lkml | Hi,
Some endpoint platforms cannot use a GIC ITS-backed MSI domain for
EP-side doorbells. In those cases, endpoint function (EPF) drivers
cannot provide a doorbell to the root complex (RC), and features such as
vNTB may fall back to polling with significantly higher latency.
This series adds an alternate doorbell bac... | null | null | null | [PATCH v9 0/7] PCI: endpoint: pci-ep-msi: Add embedded doorbell fallback | On Sat, Feb 21, 2026 at 02:42:37AM +0900, Koichiro Den wrote:
(Not 9/9 but 7/7. Sorry for the confusion.)
(Not 9/9 but 7/7. Same typo as above. Sorry.)
Koichiro | {
"author": "Koichiro Den <den@valinux.co.jp>",
"date": "Sat, 21 Feb 2026 02:59:34 +0900",
"is_openbsd": false,
"thread_id": "aaG5asXVV5sxRbnQ@ryzen.mbox.gz"
} |
lkml_critique | lkml | Hi,
Some endpoint platforms cannot use a GIC ITS-backed MSI domain for
EP-side doorbells. In those cases, endpoint function (EPF) drivers
cannot provide a doorbell to the root complex (RC), and features such as
vNTB may fall back to polling with significantly higher latency.
This series adds an alternate doorbell bac... | null | null | null | [PATCH v9 0/7] PCI: endpoint: pci-ep-msi: Add embedded doorbell fallback | On Thu, Feb 19, 2026 at 05:13:11PM +0900, Koichiro Den wrote:
(snip)
For the series:
Tested-by: Niklas Cassel <cassel@kernel.org> | {
"author": "Niklas Cassel <cassel@kernel.org>",
"date": "Fri, 27 Feb 2026 16:06:21 +0100",
"is_openbsd": false,
"thread_id": "aaG5asXVV5sxRbnQ@ryzen.mbox.gz"
} |
lkml_critique | lkml | Hi,
Some endpoint platforms cannot use a GIC ITS-backed MSI domain for
EP-side doorbells. In those cases, endpoint function (EPF) drivers
cannot provide a doorbell to the root complex (RC), and features such as
vNTB may fall back to polling with significantly higher latency.
This series adds an alternate doorbell bac... | null | null | null | [PATCH v9 0/7] PCI: endpoint: pci-ep-msi: Add embedded doorbell fallback | On Sat, Feb 21, 2026 at 02:42:35AM +0900, Koichiro Den wrote:
These patches are for NTB/vNTB:
If the diff you pasted above is all you need for pci-epf-test to pass the
doorbell test case when running against a PCI endpoint with IOMMU enabled,
then I suggest you just send a v10 with those changes included, without
an... | {
"author": "Niklas Cassel <cassel@kernel.org>",
"date": "Fri, 27 Feb 2026 16:34:02 +0100",
"is_openbsd": false,
"thread_id": "aaG5asXVV5sxRbnQ@ryzen.mbox.gz"
} |
lkml_critique | lkml | From: Li RongQing <lirongqing@baidu.com>
Currently, MTT (Memory Translation Table) buffers are allocated without
NUMA awareness using kzalloc() and vzalloc(), which allocate memory on
the NUMA node of the calling CPU. This can lead to cross-node memory
access latencies if the erdma device is attached to a different NU... | null | null | null | [PATCH][rdma-next] RDMA/erdma: Use NUMA-aware allocation for MTT tables | On 2/25/26 4:51 PM, lirongqing wrote:
Hi, Li RongQing,
Thanks for the patch. However, I think it is better to keep the current
behavior, for the following reasons:
1. This path is in the control plane, so allocating memory from a remote
NUMA node should not have a noticeable performance impact.
2. With this chang... | {
"author": "Cheng Xu <chengyou@linux.alibaba.com>",
"date": "Wed, 25 Feb 2026 19:33:49 +0800",
"is_openbsd": false,
"thread_id": "20260227145534.GL44359@ziepe.ca.mbox.gz"
} |
lkml_critique | lkml | From: Li RongQing <lirongqing@baidu.com>
Currently, MTT (Memory Translation Table) buffers are allocated without
NUMA awareness using kzalloc() and vzalloc(), which allocate memory on
the NUMA node of the calling CPU. This can lead to cross-node memory
access latencies if the erdma device is attached to a different NU... | null | null | null | [PATCH][rdma-next] RDMA/erdma: Use NUMA-aware allocation for MTT tables | When kmalloc_node() is called without __GFP_THISNODE and the target node
lacks sufficient memory, SLUB allocates a folio from a different node
other than the requested node.
So I think this is not a problem.
[Li,Rongqing] | {
"author": "\"Li,Rongqing(ACG CCN)\" <lirongqing@baidu.com>",
"date": "Wed, 25 Feb 2026 12:07:05 +0000",
"is_openbsd": false,
"thread_id": "20260227145534.GL44359@ziepe.ca.mbox.gz"
} |
lkml_critique | lkml | From: Li RongQing <lirongqing@baidu.com>
Currently, MTT (Memory Translation Table) buffers are allocated without
NUMA awareness using kzalloc() and vzalloc(), which allocate memory on
the NUMA node of the calling CPU. This can lead to cross-node memory
access latencies if the erdma device is attached to a different NU... | null | null | null | [PATCH][rdma-next] RDMA/erdma: Use NUMA-aware allocation for MTT tables | On 2/25/26 8:07 PM, Li,Rongqing(ACG CCN) wrote:
This is rarely happen in our chip.
You are right, thank you for pointing out this.
Cheng Xu | {
"author": "Cheng Xu <chengyou@linux.alibaba.com>",
"date": "Thu, 26 Feb 2026 09:50:00 +0800",
"is_openbsd": false,
"thread_id": "20260227145534.GL44359@ziepe.ca.mbox.gz"
} |
lkml_critique | lkml | From: Li RongQing <lirongqing@baidu.com>
Currently, MTT (Memory Translation Table) buffers are allocated without
NUMA awareness using kzalloc() and vzalloc(), which allocate memory on
the NUMA node of the calling CPU. This can lead to cross-node memory
access latencies if the erdma device is attached to a different NU... | null | null | null | [PATCH][rdma-next] RDMA/erdma: Use NUMA-aware allocation for MTT tables | On Thu, Feb 26, 2026 at 09:50:00AM +0800, Cheng Xu wrote:
So why do we need this patch? The xxx_node() functions are useful when you
need to force allocation on a specific NUMA node. In most cases, a plain
kmalloc() will allocate memory on the same node as 'struct erdma_dev *dev',
which typically matches the PCI devic... | {
"author": "Leon Romanovsky <leon@kernel.org>",
"date": "Thu, 26 Feb 2026 09:09:54 +0200",
"is_openbsd": false,
"thread_id": "20260227145534.GL44359@ziepe.ca.mbox.gz"
} |
lkml_critique | lkml | From: Li RongQing <lirongqing@baidu.com>
Currently, MTT (Memory Translation Table) buffers are allocated without
NUMA awareness using kzalloc() and vzalloc(), which allocate memory on
the NUMA node of the calling CPU. This can lead to cross-node memory
access latencies if the erdma device is attached to a different NU... | null | null | null | [PATCH][rdma-next] RDMA/erdma: Use NUMA-aware allocation for MTT tables | On 2/26/26 3:09 PM, Leon Romanovsky wrote:
Thanks for the detailed explanation.
Got it.
OK, I will fix this.
Thanks,
Cheng Xu | {
"author": "Cheng Xu <chengyou@linux.alibaba.com>",
"date": "Thu, 26 Feb 2026 15:59:54 +0800",
"is_openbsd": false,
"thread_id": "20260227145534.GL44359@ziepe.ca.mbox.gz"
} |
lkml_critique | lkml | From: Li RongQing <lirongqing@baidu.com>
Currently, MTT (Memory Translation Table) buffers are allocated without
NUMA awareness using kzalloc() and vzalloc(), which allocate memory on
the NUMA node of the calling CPU. This can lead to cross-node memory
access latencies if the erdma device is attached to a different NU... | null | null | null | [PATCH][rdma-next] RDMA/erdma: Use NUMA-aware allocation for MTT tables | On Thu, Feb 26, 2026 at 09:09:54AM +0200, Leon Romanovsky wrote:
I think a naked kmalloc allocates memory on the numa node of the
thread that calls it, which is not the dev's node.
IMHO it is best practice to allocate DMA'able memory from the NUMA
node of the struct device.
Jason | {
"author": "Jason Gunthorpe <jgg@ziepe.ca>",
"date": "Fri, 27 Feb 2026 10:55:34 -0400",
"is_openbsd": false,
"thread_id": "20260227145534.GL44359@ziepe.ca.mbox.gz"
} |
lkml_critique | lkml | Add bitwise or operations between the flag value enum and the underlying
type. This is useful when manipulating flags from C API without round
tripping into the Rust flag container type:
let mut lim: bindings::queue_limits = unsafe { core::mem::zeroed() };
...
if self.write_cache {
lim.features |= request:... | null | null | null | [PATCH 2/2] rust: impl_flags: add bitwise operations with the
underlying type | Add two conversion functions to the `impl_flags!` macro:
- A `From<_>` implementation to convert from the flag value enum to
underlying type.
- A `TryFrom<_> implementation to convert from the underlying
representation to flag container type.
Signed-off-by: Andreas Hindborg <a.hindborg@kernel.org>
---
rust/... | {
"author": "Andreas Hindborg <a.hindborg@kernel.org>",
"date": "Sun, 15 Feb 2026 21:22:57 +0100",
"is_openbsd": false,
"thread_id": "DGPT710WN25X.1B9P21BE6X8P4@garyguo.net.mbox.gz"
} |
lkml_critique | lkml | Add bitwise or operations between the flag value enum and the underlying
type. This is useful when manipulating flags from C API without round
tripping into the Rust flag container type:
let mut lim: bindings::queue_limits = unsafe { core::mem::zeroed() };
...
if self.write_cache {
lim.features |= request:... | null | null | null | [PATCH 2/2] rust: impl_flags: add bitwise operations with the
underlying type | Add a few convenience functions that makes it easier to work with the
`impl_flags` module and C APIs.
Signed-off-by: Andreas Hindborg <a.hindborg@kernel.org>
---
Andreas Hindborg (2):
rust: impl_flags: add conversion functions
rust: impl_flags: add bitwise operations with the underlying type
rust/kernel/... | {
"author": "Andreas Hindborg <a.hindborg@kernel.org>",
"date": "Sun, 15 Feb 2026 21:22:56 +0100",
"is_openbsd": false,
"thread_id": "DGPT710WN25X.1B9P21BE6X8P4@garyguo.net.mbox.gz"
} |
lkml_critique | lkml | Add bitwise or operations between the flag value enum and the underlying
type. This is useful when manipulating flags from C API without round
tripping into the Rust flag container type:
let mut lim: bindings::queue_limits = unsafe { core::mem::zeroed() };
...
if self.write_cache {
lim.features |= request:... | null | null | null | [PATCH 2/2] rust: impl_flags: add bitwise operations with the
underlying type | On Sun, Feb 15, 2026 at 9:23 PM Andreas Hindborg <a.hindborg@kernel.org> wrote:
Why do we need the transmute instead of a cast? Did you notice a difference?
Same in the other one -- why not constructing the object normally?
Also, you can use `Self` for `$ty` and `$flags` to make it easier to read.
In addition, I wo... | {
"author": "Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>",
"date": "Sun, 15 Feb 2026 21:53:36 +0100",
"is_openbsd": false,
"thread_id": "DGPT710WN25X.1B9P21BE6X8P4@garyguo.net.mbox.gz"
} |
lkml_critique | lkml | Add bitwise or operations between the flag value enum and the underlying
type. This is useful when manipulating flags from C API without round
tripping into the Rust flag container type:
let mut lim: bindings::queue_limits = unsafe { core::mem::zeroed() };
...
if self.write_cache {
lim.features |= request:... | null | null | null | [PATCH 2/2] rust: impl_flags: add bitwise operations with the
underlying type | On Sun Feb 15, 2026 at 8:22 PM GMT, Andreas Hindborg wrote:
I am not sure that we want to encourage direct manipulation of the underlying
bits. Adding these impls would add a surface of misuse.
Best,
Gary | {
"author": "\"Gary Guo\" <gary@garyguo.net>",
"date": "Fri, 27 Feb 2026 14:20:46 +0000",
"is_openbsd": false,
"thread_id": "DGPT710WN25X.1B9P21BE6X8P4@garyguo.net.mbox.gz"
} |
lkml_critique | lkml | V2 patch incorporating feedback from previous discussion:
- per-inode atomic cursors to enforce stream sequentiality
- per-CPU starting points to reduce contention
- allocator isolation maintained; regular allocator untouched
- name changed to rralloc to avoid confusion with "rotational"
- preliminary tests confirm ex... | null | null | null | [PATCH] ext4: rralloc - (former rotalloc) improved round-robin allocation policy | On Feb 25, 2026, at 13:15, Mario Lohajner <mario_lohajner@rocketmail.com> wrote:
Mario, can you please include a summary of the performance test
results into the commit message so that the effectiveness of the
patch can be evaluated. This should include test(s) run and
their arguments, along with table of before/afte... | {
"author": "Andreas Dilger <adilger@dilger.ca>",
"date": "Wed, 25 Feb 2026 16:49:30 -0700",
"is_openbsd": false,
"thread_id": "2af6328d-5a72-476d-9768-9398a9417ea6@rocketmail.com.mbox.gz"
} |
lkml_critique | lkml | V2 patch incorporating feedback from previous discussion:
- per-inode atomic cursors to enforce stream sequentiality
- per-CPU starting points to reduce contention
- allocator isolation maintained; regular allocator untouched
- name changed to rralloc to avoid confusion with "rotational"
- preliminary tests confirm ex... | null | null | null | [PATCH] ext4: rralloc - (former rotalloc) improved round-robin allocation policy | On Wed, Feb 25, 2026 at 04:49:30PM -0700, Andreas Dilger wrote:
The tests should also include an explanation of the hardware that you
ran the test on. Some example of cover letters that include
perforance improvement results:
https://lore.kernel.org/all/20251025032221.2905818-1-libaokun@huaweicloud.com/
https://lore... | {
"author": "\"Theodore Tso\" <tytso@mit.edu>",
"date": "Wed, 25 Feb 2026 21:48:19 -0500",
"is_openbsd": false,
"thread_id": "2af6328d-5a72-476d-9768-9398a9417ea6@rocketmail.com.mbox.gz"
} |
lkml_critique | lkml | V2 patch incorporating feedback from previous discussion:
- per-inode atomic cursors to enforce stream sequentiality
- per-CPU starting points to reduce contention
- allocator isolation maintained; regular allocator untouched
- name changed to rralloc to avoid confusion with "rotational"
- preliminary tests confirm ex... | null | null | null | [PATCH] ext4: rralloc - (former rotalloc) improved round-robin allocation policy | On 26. 02. 2026. 03:48, Theodore Tso wrote:
Hello Andreas, hello Theodore!
These are the results of synthetic tests designed to evaluate whether
the round-robin allocator (rralloc) maintains its allocation behavior
without degrading performance, and to examine its behavior under high
concurrency and stress conditions... | {
"author": "Mario Lohajner <mario_lohajner@rocketmail.com>",
"date": "Thu, 26 Feb 2026 22:50:29 +0100",
"is_openbsd": false,
"thread_id": "2af6328d-5a72-476d-9768-9398a9417ea6@rocketmail.com.mbox.gz"
} |
lkml_critique | lkml | V2 patch incorporating feedback from previous discussion:
- per-inode atomic cursors to enforce stream sequentiality
- per-CPU starting points to reduce contention
- allocator isolation maintained; regular allocator untouched
- name changed to rralloc to avoid confusion with "rotational"
- preliminary tests confirm ex... | null | null | null | [PATCH] ext4: rralloc - (former rotalloc) improved round-robin allocation policy | On Thu, Feb 26, 2026 at 10:50:29PM +0100, Mario Lohajner wrote:
You haven't explained *why* allocation distribution and avoiding
hotspotting is something we should care about.
If it's not performance, then why? How does reducing hotspotting
improve things for the user? Why should we care about this goal that
appare... | {
"author": "\"Theodore Tso\" <tytso@mit.edu>",
"date": "Thu, 26 Feb 2026 20:12:00 -0500",
"is_openbsd": false,
"thread_id": "2af6328d-5a72-476d-9768-9398a9417ea6@rocketmail.com.mbox.gz"
} |
lkml_critique | lkml | V2 patch incorporating feedback from previous discussion:
- per-inode atomic cursors to enforce stream sequentiality
- per-CPU starting points to reduce contention
- allocator isolation maintained; regular allocator untouched
- name changed to rralloc to avoid confusion with "rotational"
- preliminary tests confirm ex... | null | null | null | [PATCH] ext4: rralloc - (former rotalloc) improved round-robin allocation policy | On 27. 02. 2026. 02:12, Theodore Tso wrote:
Hello Ted,
The motivation behind rralloc is to promote even allocation across the
available LBA under overwrite-heavy workloads.
With the regular allocator, repeated allocations can concentrate the
pressure in specific regions (e.g., in-place overwrites or LBA start).
rra... | {
"author": "Mario Lohajner <mario_lohajner@rocketmail.com>",
"date": "Fri, 27 Feb 2026 15:46:59 +0100",
"is_openbsd": false,
"thread_id": "2af6328d-5a72-476d-9768-9398a9417ea6@rocketmail.com.mbox.gz"
} |
lkml_critique | lkml | Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
previleged level to access to access user memory without clearing
PSTATE.PAN bit.
This patchset support FEAT_LSUI and applies it mainly in
futex atomic operation and others.
This patch based on v7.0-rc1
Patch History
==============
from v14 to v15:
... | null | null | null | [PATCH v15 0/8] support FEAT_LSUI | Since Armv9.6, FEAT_LSUI introduces load/store instructions that allow
privileged code to access user memory without clearing the PSTATE.PAN bit.
Add CPU feature detection for FEAT_LSUI and enable its use
when FEAT_PAN is present so that removes the need for SW_PAN handling
when using LSUI instructions.
Signed-off-by... | {
"author": "Yeoreum Yun <yeoreum.yun@arm.com>",
"date": "Fri, 27 Feb 2026 15:16:58 +0000",
"is_openbsd": false,
"thread_id": "20260227151705.1275328-4-yeoreum.yun@arm.com.mbox.gz"
} |
lkml_critique | lkml | Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
previleged level to access to access user memory without clearing
PSTATE.PAN bit.
This patchset support FEAT_LSUI and applies it mainly in
futex atomic operation and others.
This patch based on v7.0-rc1
Patch History
==============
from v14 to v15:
... | null | null | null | [PATCH v15 0/8] support FEAT_LSUI | expose FEAT_LSUI to guest.
Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
Acked-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
---
arch/arm64/kvm/sys_regs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_... | {
"author": "Yeoreum Yun <yeoreum.yun@arm.com>",
"date": "Fri, 27 Feb 2026 15:16:59 +0000",
"is_openbsd": false,
"thread_id": "20260227151705.1275328-4-yeoreum.yun@arm.com.mbox.gz"
} |
lkml_critique | lkml | Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
previleged level to access to access user memory without clearing
PSTATE.PAN bit.
This patchset support FEAT_LSUI and applies it mainly in
futex atomic operation and others.
This patch based on v7.0-rc1
Patch History
==============
from v14 to v15:
... | null | null | null | [PATCH v15 0/8] support FEAT_LSUI | Add test coverage for FEAT_LSUI.
Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
Reviewed-by: Mark Brown <broonie@kernel.org>
---
tools/testing/selftests/kvm/arm64/set_id_regs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/kvm/arm64/set_id_regs.c b/tools/testing/selftests/kvm/arm64/set... | {
"author": "Yeoreum Yun <yeoreum.yun@arm.com>",
"date": "Fri, 27 Feb 2026 15:17:00 +0000",
"is_openbsd": false,
"thread_id": "20260227151705.1275328-4-yeoreum.yun@arm.com.mbox.gz"
} |
lkml_critique | lkml | Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
previleged level to access to access user memory without clearing
PSTATE.PAN bit.
This patchset support FEAT_LSUI and applies it mainly in
futex atomic operation and others.
This patch based on v7.0-rc1
Patch History
==============
from v14 to v15:
... | null | null | null | [PATCH v15 0/8] support FEAT_LSUI | Refactor futex atomic operations using ll/sc method with
clearing PSTATE.PAN to prepare to apply FEAT_LSUI on them.
Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
---
arch/arm64/include/asm/futex.h | 137 +++++++++++++++++++++------------
1 file changed, 87 ins... | {
"author": "Yeoreum Yun <yeoreum.yun@arm.com>",
"date": "Fri, 27 Feb 2026 15:17:01 +0000",
"is_openbsd": false,
"thread_id": "20260227151705.1275328-4-yeoreum.yun@arm.com.mbox.gz"
} |
lkml_critique | lkml | Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
previleged level to access to access user memory without clearing
PSTATE.PAN bit.
This patchset support FEAT_LSUI and applies it mainly in
futex atomic operation and others.
This patch based on v7.0-rc1
Patch History
==============
from v14 to v15:
... | null | null | null | [PATCH v15 0/8] support FEAT_LSUI | Current futex atomic operations are implemented with ll/sc instructions
and clearing PSTATE.PAN.
Since Armv9.6, FEAT_LSUI supplies not only load/store instructions but
also atomic operation for user memory access in kernel it doesn't need
to clear PSTATE.PAN bit anymore.
With theses instructions some of futex atomic ... | {
"author": "Yeoreum Yun <yeoreum.yun@arm.com>",
"date": "Fri, 27 Feb 2026 15:17:02 +0000",
"is_openbsd": false,
"thread_id": "20260227151705.1275328-4-yeoreum.yun@arm.com.mbox.gz"
} |
lkml_critique | lkml | Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
previleged level to access to access user memory without clearing
PSTATE.PAN bit.
This patchset support FEAT_LSUI and applies it mainly in
futex atomic operation and others.
This patch based on v7.0-rc1
Patch History
==============
from v14 to v15:
... | null | null | null | [PATCH v15 0/8] support FEAT_LSUI | The purpose of supporting LSUI is to eliminate PAN toggling.
CPUs that support LSUI are unlikely to support a 32-bit runtime.
Since environments that support both LSUI and
a 32-bit runtimeare expected to be extremely rare,
not to emulate the SWP instruction using LSUI instructions
in order to remove PAN toggling, and i... | {
"author": "Yeoreum Yun <yeoreum.yun@arm.com>",
"date": "Fri, 27 Feb 2026 15:17:03 +0000",
"is_openbsd": false,
"thread_id": "20260227151705.1275328-4-yeoreum.yun@arm.com.mbox.gz"
} |
lkml_critique | lkml | Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
previleged level to access to access user memory without clearing
PSTATE.PAN bit.
This patchset support FEAT_LSUI and applies it mainly in
futex atomic operation and others.
This patch based on v7.0-rc1
Patch History
==============
from v14 to v15:
... | null | null | null | [PATCH v15 0/8] support FEAT_LSUI | Use the CAST instruction to swap the guest descriptor when FEAT_LSUI
is enabled, avoiding the need to clear the PAN bit.
Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
---
arch/arm64/kvm/at.c | 42 +++++++++++++++++++++++++++++++++++++++++-
1 file changed, 41 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/kv... | {
"author": "Yeoreum Yun <yeoreum.yun@arm.com>",
"date": "Fri, 27 Feb 2026 15:17:04 +0000",
"is_openbsd": false,
"thread_id": "20260227151705.1275328-4-yeoreum.yun@arm.com.mbox.gz"
} |
lkml_critique | lkml | Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
previleged level to access to access user memory without clearing
PSTATE.PAN bit.
This patchset support FEAT_LSUI and applies it mainly in
futex atomic operation and others.
This patch based on v7.0-rc1
Patch History
==============
from v14 to v15:
... | null | null | null | [PATCH v15 0/8] support FEAT_LSUI | Since Armv9.6, FEAT_LSUI supplies the load/store instructions for
previleged level to access to access user memory without clearing
PSTATE.PAN bit.
Add Kconfig option entry for FEAT_LSUI.
Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
---
arch/arm64/Kconfig | ... | {
"author": "Yeoreum Yun <yeoreum.yun@arm.com>",
"date": "Fri, 27 Feb 2026 15:17:05 +0000",
"is_openbsd": false,
"thread_id": "20260227151705.1275328-4-yeoreum.yun@arm.com.mbox.gz"
} |
lkml_critique | lkml | This fixes xfstests generic/451 (for both O_DIRECT and FOPEN_DIRECT_IO
direct write).
Commit b359af8275a9 ("fuse: Invalidate the page cache after
FOPEN_DIRECT_IO write") tries to fix the similar issue for
FOPEN_DIRECT_IO write, which can be reproduced by xfstests generic/209.
It only fixes the issue for synchronous di... | null | null | null | [PATCH v3] fuse: invalidate the page cache after direct write | …
…
…
- return err ?: ia->write.out.size;
…
You may omit curly brackets at selected source code places.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-style.rst?h=v6.19-rc4#n197
Regards,
Markus | {
"author": "Markus Elfring <Markus.Elfring@web.de>",
"date": "Sun, 11 Jan 2026 09:18:46 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegtS+rX37qLVPW+Ciso_+yqjTqGKNnvSacpd7HdniGXjAQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | This fixes xfstests generic/451 (for both O_DIRECT and FOPEN_DIRECT_IO
direct write).
Commit b359af8275a9 ("fuse: Invalidate the page cache after
FOPEN_DIRECT_IO write") tries to fix the similar issue for
FOPEN_DIRECT_IO write, which can be reproduced by xfstests generic/209.
It only fixes the issue for synchronous di... | null | null | null | [PATCH v3] fuse: invalidate the page cache after direct write | On 1/11/26 09:18, Markus Elfring wrote:
We could, but we could also concentrate on code correctness instead of
nit-picky debatable code style.
Thanks,
Bernd | {
"author": "Bernd Schubert <bschubert@ddn.com>",
"date": "Sun, 11 Jan 2026 10:43:43 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegtS+rX37qLVPW+Ciso_+yqjTqGKNnvSacpd7HdniGXjAQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | This fixes xfstests generic/451 (for both O_DIRECT and FOPEN_DIRECT_IO
direct write).
Commit b359af8275a9 ("fuse: Invalidate the page cache after
FOPEN_DIRECT_IO write") tries to fix the similar issue for
FOPEN_DIRECT_IO write, which can be reproduced by xfstests generic/209.
It only fixes the issue for synchronous di... | null | null | null | [PATCH v3] fuse: invalidate the page cache after direct write | On 1/11/26 4:18 PM, Markus Elfring wrote:
It's generally true for **simple** single statement. I would prefer
adding the braces as it's a multi-line statement with a comment block.
--
Thanks,
Jingbo | {
"author": "Jingbo Xu <jefflexu@linux.alibaba.com>",
"date": "Mon, 12 Jan 2026 13:37:12 +0800",
"is_openbsd": false,
"thread_id": "CAJfpegtS+rX37qLVPW+Ciso_+yqjTqGKNnvSacpd7HdniGXjAQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | This fixes xfstests generic/451 (for both O_DIRECT and FOPEN_DIRECT_IO
direct write).
Commit b359af8275a9 ("fuse: Invalidate the page cache after
FOPEN_DIRECT_IO write") tries to fix the similar issue for
FOPEN_DIRECT_IO write, which can be reproduced by xfstests generic/209.
It only fixes the issue for synchronous di... | null | null | null | [PATCH v3] fuse: invalidate the page cache after direct write | On Sun, 11 Jan 2026 at 08:37, Jingbo Xu <jefflexu@linux.alibaba.com> wrote:
Applied, thanks.
Miklos | {
"author": "Miklos Szeredi <miklos@szeredi.hu>",
"date": "Fri, 27 Feb 2026 16:09:05 +0100",
"is_openbsd": false,
"thread_id": "CAJfpegtS+rX37qLVPW+Ciso_+yqjTqGKNnvSacpd7HdniGXjAQ@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | This series addresses several compiler warnings found when building the
kernel for RISC-V.
The first patch fixes unused variable warnings in the NFS client (including
nfs4proc and flexfilelayout) that occur in certain build configurations.
The second patch fixes a format-truncation warning in the MACB ethernet
driver... | null | null | null | [PATCH v4 0/2] Fix warnings for RISC-V builds | When CONFIG_SUNRPC_DEBUG is disabled, the dfprintk() macros currently
expand to empty do-while loops. This causes variables used solely
within these calls to appear unused, triggering -Wunused-variable
warnings.
Instead of marking every affected variable with __maybe_unused,
update the dfprintk and dfprintk_rcu stubs ... | {
"author": "Sean Chang <seanwascoding@gmail.com>",
"date": "Fri, 27 Feb 2026 23:26:23 +0800",
"is_openbsd": false,
"thread_id": "20260227152624.164964-2-seanwascoding@gmail.com.mbox.gz"
} |
lkml_critique | lkml | This series addresses several compiler warnings found when building the
kernel for RISC-V.
The first patch fixes unused variable warnings in the NFS client (including
nfs4proc and flexfilelayout) that occur in certain build configurations.
The second patch fixes a format-truncation warning in the MACB ethernet
driver... | null | null | null | [PATCH v4 0/2] Fix warnings for RISC-V builds | The RISC-V toolchain triggers a stringop-truncation warning when using
snprintf() with a fixed ETH_GSTRING_LEN (32 bytes) buffer.
Convert the driver to use the modern ethtool_sprintf() API from
linux/ethtool.h. This removes the need for manual snprintf() and
memcpy() calls, handles the 32-byte padding automatically, a... | {
"author": "Sean Chang <seanwascoding@gmail.com>",
"date": "Fri, 27 Feb 2026 23:26:24 +0800",
"is_openbsd": false,
"thread_id": "20260227152624.164964-2-seanwascoding@gmail.com.mbox.gz"
} |
lkml_critique | lkml | Move netdev registration and notifier block registration from
sparx5_start() to probe(). This allows proper cleanup via goto-based
error labels in probe().
Also, remove the sparx5_cleanup_ports() helper as its functionality is now
split between sparx5_unregister_netdevs() and sparx5_destroy_netdevs()
called at appropr... | null | null | null | [PATCH net-next v2 1/9] net: sparx5: move netdev and notifier
block registration to probe | This series refactors the sparx5 init and deinit code out of
sparx5_start() and into probe(), adding proper per-subsystem cleanup
labels and deinit functions.
Currently, the sparx5 driver initializes most subsystems inside
sparx5_start(), which is called from probe(). This includes registering
netdevs, starting worker... | {
"author": "Daniel Machon <daniel.machon@microchip.com>",
"date": "Fri, 27 Feb 2026 15:56:38 +0100",
"is_openbsd": false,
"thread_id": "20260227-sparx5-init-deinit-v2-6-10ba54ccf005@microchip.com.mbox.gz"
} |
lkml_critique | lkml | Move netdev registration and notifier block registration from
sparx5_start() to probe(). This allows proper cleanup via goto-based
error labels in probe().
Also, remove the sparx5_cleanup_ports() helper as its functionality is now
split between sparx5_unregister_netdevs() and sparx5_destroy_netdevs()
called at appropr... | null | null | null | [PATCH net-next v2 1/9] net: sparx5: move netdev and notifier
block registration to probe | The sparx5_stats_init() function starts a worker thread which needs to
be cleaned up. Move the initialization code to probe() and add a
deinit() function for proper teardown.
Also, rename sparx_stats_init() to sparx5_stats_init() to match the
driver naming convention.
Signed-off-by: Daniel Machon <daniel.machon@micro... | {
"author": "Daniel Machon <daniel.machon@microchip.com>",
"date": "Fri, 27 Feb 2026 15:56:42 +0100",
"is_openbsd": false,
"thread_id": "20260227-sparx5-init-deinit-v2-6-10ba54ccf005@microchip.com.mbox.gz"
} |
lkml_critique | lkml | Move netdev registration and notifier block registration from
sparx5_start() to probe(). This allows proper cleanup via goto-based
error labels in probe().
Also, remove the sparx5_cleanup_ports() helper as its functionality is now
split between sparx5_unregister_netdevs() and sparx5_destroy_netdevs()
called at appropr... | null | null | null | [PATCH net-next v2 1/9] net: sparx5: move netdev and notifier
block registration to probe | Move the calendar initialization from sparx5_start() to probe() by
creating a new sparx5_calendar_init() wrapper function that calls both
sparx5_config_auto_calendar() and sparx5_config_dsm_calendar().
Calendar initialization does not require cleanup.
Also, make the individual calendar config functions static since th... | {
"author": "Daniel Machon <daniel.machon@microchip.com>",
"date": "Fri, 27 Feb 2026 15:56:43 +0100",
"is_openbsd": false,
"thread_id": "20260227-sparx5-init-deinit-v2-6-10ba54ccf005@microchip.com.mbox.gz"
} |
lkml_critique | lkml | Move netdev registration and notifier block registration from
sparx5_start() to probe(). This allows proper cleanup via goto-based
error labels in probe().
Also, remove the sparx5_cleanup_ports() helper as its functionality is now
split between sparx5_unregister_netdevs() and sparx5_destroy_netdevs()
called at appropr... | null | null | null | [PATCH net-next v2 1/9] net: sparx5: move netdev and notifier
block registration to probe | Move the PTP IRQ request into sparx5_ptp_init() so all PTP setup is
done in one place.
Also move the sparx5_ptp_init() call to right before
sparx5_register_netdevs() and add a cleanup_ptp label. Update remove()
to disable the PTP IRQ and reorder ptp_deinit accordingly.
Signed-off-by: Daniel Machon <daniel.machon@micr... | {
"author": "Daniel Machon <daniel.machon@microchip.com>",
"date": "Fri, 27 Feb 2026 15:56:45 +0100",
"is_openbsd": false,
"thread_id": "20260227-sparx5-init-deinit-v2-6-10ba54ccf005@microchip.com.mbox.gz"
} |
lkml_critique | lkml | Move netdev registration and notifier block registration from
sparx5_start() to probe(). This allows proper cleanup via goto-based
error labels in probe().
Also, remove the sparx5_cleanup_ports() helper as its functionality is now
split between sparx5_unregister_netdevs() and sparx5_destroy_netdevs()
called at appropr... | null | null | null | [PATCH net-next v2 1/9] net: sparx5: move netdev and notifier
block registration to probe | Move the VCAP initialization code from sparx5_start() to probe(). Add
proper error handling with a cleanup_vcap label and sparx5_vcap_deinit()
call.
Also, rename sparx5_vcap_destroy() to sparx5_vcap_deinit() to stay
consistent with the naming.
Signed-off-by: Daniel Machon <daniel.machon@microchip.com>
---
drivers/ne... | {
"author": "Daniel Machon <daniel.machon@microchip.com>",
"date": "Fri, 27 Feb 2026 15:56:40 +0100",
"is_openbsd": false,
"thread_id": "20260227-sparx5-init-deinit-v2-6-10ba54ccf005@microchip.com.mbox.gz"
} |
lkml_critique | lkml | Move netdev registration and notifier block registration from
sparx5_start() to probe(). This allows proper cleanup via goto-based
error labels in probe().
Also, remove the sparx5_cleanup_ports() helper as its functionality is now
split between sparx5_unregister_netdevs() and sparx5_destroy_netdevs()
called at appropr... | null | null | null | [PATCH net-next v2 1/9] net: sparx5: move netdev and notifier
block registration to probe | Move sparx5_pgid_init(), sparx5_vlan_init(), and sparx5_board_init()
from sparx5_start() to probe(). These functions do not require cleanup.
Signed-off-by: Daniel Machon <daniel.machon@microchip.com>
---
drivers/net/ethernet/microchip/sparx5/sparx5_main.c | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletion... | {
"author": "Daniel Machon <daniel.machon@microchip.com>",
"date": "Fri, 27 Feb 2026 15:56:44 +0100",
"is_openbsd": false,
"thread_id": "20260227-sparx5-init-deinit-v2-6-10ba54ccf005@microchip.com.mbox.gz"
} |
lkml_critique | lkml | Move netdev registration and notifier block registration from
sparx5_start() to probe(). This allows proper cleanup via goto-based
error labels in probe().
Also, remove the sparx5_cleanup_ports() helper as its functionality is now
split between sparx5_unregister_netdevs() and sparx5_destroy_netdevs()
called at appropr... | null | null | null | [PATCH net-next v2 1/9] net: sparx5: move netdev and notifier
block registration to probe | Move the Frame DMA and register-based extraction initialization out of
sparx5_start() and into a new sparx5_frame_io_init() function, called
from probe().
Also, add sparx5_frame_io_deinit() for the cleanup path.
Signed-off-by: Daniel Machon <daniel.machon@microchip.com>
---
.../net/ethernet/microchip/sparx5/sparx5_m... | {
"author": "Daniel Machon <daniel.machon@microchip.com>",
"date": "Fri, 27 Feb 2026 15:56:46 +0100",
"is_openbsd": false,
"thread_id": "20260227-sparx5-init-deinit-v2-6-10ba54ccf005@microchip.com.mbox.gz"
} |
lkml_critique | lkml | Move netdev registration and notifier block registration from
sparx5_start() to probe(). This allows proper cleanup via goto-based
error labels in probe().
Also, remove the sparx5_cleanup_ports() helper as its functionality is now
split between sparx5_unregister_netdevs() and sparx5_destroy_netdevs()
called at appropr... | null | null | null | [PATCH net-next v2 1/9] net: sparx5: move netdev and notifier
block registration to probe | With all subsystem initializations moved out, sparx5_start() only sets
up forwarding (UPSIDs, CPU ports, masks, PGIDs, FCS, watermarks).
Rename it to sparx5_forwarding_init() and make it void since it cannot
fail. This removes sparx5_start() entirely.
Signed-off-by: Daniel Machon <daniel.machon@microchip.com>
---
dri... | {
"author": "Daniel Machon <daniel.machon@microchip.com>",
"date": "Fri, 27 Feb 2026 15:56:47 +0100",
"is_openbsd": false,
"thread_id": "20260227-sparx5-init-deinit-v2-6-10ba54ccf005@microchip.com.mbox.gz"
} |
lkml_critique | lkml | Move netdev registration and notifier block registration from
sparx5_start() to probe(). This allows proper cleanup via goto-based
error labels in probe().
Also, remove the sparx5_cleanup_ports() helper as its functionality is now
split between sparx5_unregister_netdevs() and sparx5_destroy_netdevs()
called at appropr... | null | null | null | [PATCH net-next v2 1/9] net: sparx5: move netdev and notifier
block registration to probe | Consolidate all MAC table initialization from sparx5_start() into
sparx5_mact_init(), move it to probe(), and add a deinit function for
proper teardown.
Also, make sparx5_mact_pull_work() static since it is only used within
sparx5_mactable.c.
Signed-off-by: Daniel Machon <daniel.machon@microchip.com>
---
.../etherne... | {
"author": "Daniel Machon <daniel.machon@microchip.com>",
"date": "Fri, 27 Feb 2026 15:56:41 +0100",
"is_openbsd": false,
"thread_id": "20260227-sparx5-init-deinit-v2-6-10ba54ccf005@microchip.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | Windows implements a DSM called "Turn On Display". This notification is
sent to the hardware while on the sleep state if the user interacted
with the device and caused it to wake up in such a way where the display
should turn on.
This allows the OEM to counter the effects of Sleep entry such as a
reduced power envelop... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Fri, 26 Dec 2025 12:26:44 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | Implement the standby states as part of hibernation. Specifically,
ensure we are in the inactive state before hibernation entry, and
sync the state as active after hibernation resume. In case of a failed
hibernation, restore the previous standby state.
Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
---
kernel/... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Fri, 26 Dec 2025 12:26:45 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | Add a sysfs attribute to allow informing the kernel about the current
standby state of the device depending on user involvement, those being:
"active", "inactive", "sleep", and "resume" (in "sleep" but preparing
for presenting to the user faster).
Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
---
kernel/power... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Fri, 26 Dec 2025 12:26:46 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | Implement the platform_s2idle_ops->get_standby_states() callback to
query which modern standby states are supported by the platform based
on the dsm func masks and expose those to the kernel as runtime standby
states. Union the vendor specific AMD/Intel masks with the ones from
Microsoft as some laptops implement both ... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Fri, 26 Dec 2025 12:26:42 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | This series introduces a new runtime standby ABI to allow firing Modern
Standby firmware notifications that modify hardware appearance from userspace
without suspending the kernel. This allows userspace to set the inactivity
state of the device so that it looks like it is asleep (e.g., flashing the
power button) while ... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Fri, 26 Dec 2025 12:26:38 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | Add pm_standby_transition() to allow transitioning between standby
states during runtime and implement it as part of the s2idle suspend
sequence. Update the platform_s2idle_ops structure to include a function
to perform firmware notifications and a function to get supported states
Standby states are a way for userspac... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Fri, 26 Dec 2025 12:26:41 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | Currently, the DSM Sleep Entry/Exit/Display On/Off notifications fire
during the suspend sequence. Move them to the new do_notification
callback so they can be called during runtime as well. The kernel will
still ensure that they are called during s2idle without userspace
involvement.
Signed-off-by: Antheas Kapenekaki... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Fri, 26 Dec 2025 12:26:43 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | Introduce the runtime standby state ABI, which allows for firing the
Modern Standby firmware notifications found in Windows during runtime.
These notifications allow to make systems that support them look
suspended.
Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
---
Documentation/ABI/testing/sysfs-power ... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Fri, 26 Dec 2025 12:26:39 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | On Fri, 26 Dec 2025 at 12:27, Antheas Kapenekakis <lkml@antheas.dev> wrote:
Happy new year everyone
Small bump on this as all of us are starting to get back from holidays
I still have to bump an asus series before I get back to this. I would
appreciate some feedback in the interim.
I think targeting 6.20/7.0? is un... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Mon, 12 Jan 2026 22:33:06 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | Hello,
On 1/12/26 23:33, Antheas Kapenekakis wrote:
Thanks a lot for sending these patches! I briefly looked through them
last week and will make another iteration soon.
--
Best regards,
Dmitry | {
"author": "Dmitry Osipenko <dmitry.osipenko@collabora.com>",
"date": "Tue, 13 Jan 2026 12:48:30 +0300",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | On Tue, 13 Jan 2026 at 11:50, Dmitry Osipenko
<dmitry.osipenko@collabora.com> wrote:
Hi Dmitry,
can you expand a bit on your use-case/KPIs/timeline for your series?
Is it handhelds/laptops or what is the intended use-case?
[2] before the rewrite had been tested on most handheld makes and SKUs
(over 70 models) and la... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Tue, 13 Jan 2026 12:11:33 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | On 1/13/26 13:11, Antheas Kapenekakis wrote:
The primary goal is to support screen-off DSM for a power-efficient
background games downloading [1] and further resume-to-dark on Steam
Deck and other handhelds. There is no strict timeline, usual "sooner the
better". Downstreams will use customized WIP solution till upstr... | {
"author": "Dmitry Osipenko <dmitry.osipenko@collabora.com>",
"date": "Thu, 15 Jan 2026 02:07:02 +0300",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | On Thu, 15 Jan 2026 at 01:07, Dmitry Osipenko
<dmitry.osipenko@collabora.com> wrote:
Hi Dmitry,
let me go inline.
Ok, this makes things clearer. I had done some testing to see the
viability of such approach.
One big problem [1] had was that the compression algorithm that Steam
used was very CPU intensive. However, ... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Thu, 15 Jan 2026 09:49:15 +0200",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | The LPS0 3/4 constants are part of a firmware notification called
"Display on/off", in which the device enters a "Screen Off" state.
The LPS0 7/8 constants are part of a firmware notification in which
a Windows modern standby computer enters a "sleep" state where the
CPU may still be active and maintain the radios.
Ho... | null | null | null | [RFC v1 2/8] acpi/x86: s2idle: Rename LPS0 constants so they mirror
their function | Hi everyone,
now that the kernel merge window is over, I will slowly get back to
cleaning this series up
I already have some feedback that I will address with V2.
Specifically, we found out that the resume DSM needs to always be
called and it merged with 7.0. So I will rebase on top of it, remove
the patch that added... | {
"author": "Antheas Kapenekakis <lkml@antheas.dev>",
"date": "Fri, 27 Feb 2026 15:59:46 +0100",
"is_openbsd": false,
"thread_id": "CAGwozwHE4DVCh79-523V5=a_fqR0gXnnkorGCPEsgHBDLYPtxA@mail.gmail.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | Zone lock contention can significantly impact allocation and
reclaim latency, as it is a central synchronization point in
the page allocator and reclaim paths. Improved visibility into
its behavior is therefore important for diagnosing performance
issues in memory-intensive workloads.
On some production workloads at M... | {
"author": "Dmitry Ilvokhin <d@ilvokhin.com>",
"date": "Thu, 26 Feb 2026 18:26:17 +0000",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | Compaction uses compact_lock_irqsave(), which currently operates
on a raw spinlock_t pointer so it can be used for both zone->lock
and lruvec->lru_lock. Since zone lock operations are now wrapped,
compact_lock_irqsave() can no longer directly operate on a
spinlock_t when the lock belongs to a zone.
Split the helper in... | {
"author": "Dmitry Ilvokhin <d@ilvokhin.com>",
"date": "Thu, 26 Feb 2026 18:26:20 +0000",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | This intentionally breaks direct users of zone->lock at compile time so
all call sites are converted to the zone lock wrappers. Without the
rename, present and future out-of-tree code could continue using
spin_lock(&zone->lock) and bypass the wrappers and tracing
infrastructure.
No functional change intended.
Suggest... | {
"author": "Dmitry Ilvokhin <d@ilvokhin.com>",
"date": "Thu, 26 Feb 2026 18:26:21 +0000",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | Add tracepoint instrumentation to zone lock acquire/release operations
via the previously introduced wrappers.
The implementation follows the mmap_lock tracepoint pattern: a
lightweight inline helper checks whether the tracepoint is enabled and
calls into an out-of-line helper when tracing is active. When
CONFIG_TRACI... | {
"author": "Dmitry Ilvokhin <d@ilvokhin.com>",
"date": "Thu, 26 Feb 2026 18:26:22 +0000",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | Replace direct zone lock acquire/release operations with the
newly introduced wrappers.
The changes are purely mechanical substitutions. No functional change
intended. Locking semantics and ordering remain unchanged.
The compaction path is left unchanged for now and will be
handled separately in the following patch d... | {
"author": "Dmitry Ilvokhin <d@ilvokhin.com>",
"date": "Thu, 26 Feb 2026 18:26:19 +0000",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, Feb 26, 2026 at 06:26:20PM +0000, Dmitry Ilvokhin wrote:
Acked-by: Shakeel Butt <shakeel.butt@linux.dev> | {
"author": "Shakeel Butt <shakeel.butt@linux.dev>",
"date": "Thu, 26 Feb 2026 11:07:47 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, Feb 26, 2026 at 06:26:21PM +0000, Dmitry Ilvokhin wrote:
Acked-by: Shakeel Butt <shakeel.butt@linux.dev> | {
"author": "Shakeel Butt <shakeel.butt@linux.dev>",
"date": "Thu, 26 Feb 2026 11:09:59 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, Feb 26, 2026 at 06:26:22PM +0000, Dmitry Ilvokhin wrote:
One nit below other than that:
Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
[...]
No reason to not have these as EXPORT_SYMBOL_GPL (& below) | {
"author": "Shakeel Butt <shakeel.butt@linux.dev>",
"date": "Thu, 26 Feb 2026 11:14:52 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, 26 Feb 2026 11:14:52 -0800 Shakeel Butt <shakeel.butt@linux.dev> wrote:
Do we need the exports at all?
include/linux/mmzone.h
include/linux/zone_lock.h
include/trace/events/zone_lock.h
MAINTAINERS
mm/compaction.c
mm/internal.h
mm/Makefile
mm/memory_hotplug.c
mm/mm_init.c
mm/page_alloc.c
mm/page_isolation.c
m... | {
"author": "Andrew Morton <akpm@linux-foundation.org>",
"date": "Thu, 26 Feb 2026 13:25:01 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, Feb 26, 2026 at 01:25:01PM -0800, Andrew Morton wrote:
Very good point and we don't. I think this might just be copying the mmap_lock
tracepoint wrappers which might need the exports as some drivers might be taking
the mmap_lock.
Dmitry, please confirm (test) and let us know. | {
"author": "Shakeel Butt <shakeel.butt@linux.dev>",
"date": "Thu, 26 Feb 2026 13:31:48 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | Hi Dmitry,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v7.0-rc1 next-20260226]
[cannot apply to akpm-mm/mm-everything rppt-memblock/for-next rppt-memblock/fixes]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Fri, 27 Feb 2026 05:48:05 +0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Fri, 27 Feb 2026 05:48:05 +0800 kernel test robot <lkp@intel.com> wrote:
yep, thanks. And kernel/power/snapshot.c. I've added fixups. | {
"author": "Andrew Morton <akpm@linux-foundation.org>",
"date": "Thu, 26 Feb 2026 14:08:46 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | Hi Dmitry,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v7.0-rc1 next-20260226]
[cannot apply to akpm-mm/mm-everything rppt-memblock/for-next rppt-memblock/fixes]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Fri, 27 Feb 2026 07:13:01 +0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, 26 Feb 2026 18:26:18 +0000 Dmitry Ilvokhin <d@ilvokhin.com> wrote:
I'm bit worried if I will think this as a file for another general locking, not
the mm specific one. I hence think renaming it to more clearly saying the
fact, say, mmzone_lock.h, might be less confusing. Or, putting things in
mmzone.h might... | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Thu, 26 Feb 2026 16:31:39 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | I should sent this together with the previous reply, but I forgot as usual,
sorry.
On Thu, 26 Feb 2026 18:26:18 +0000 Dmitry Ilvokhin <d@ilvokhin.com> wrote:
[...]
checkpatch.pl complains as below. Should be ok to ignore, but, may better to
kindly make it silence?
WARNING: Single statement macros should not us... | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Thu, 26 Feb 2026 16:38:55 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, 26 Feb 2026 18:26:19 +0000 Dmitry Ilvokhin <d@ilvokhin.com> wrote:
Reviewed-by: SeongJae Park <sj@kernel.org>
Thanks,
SJ
[...] | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Thu, 26 Feb 2026 16:40:02 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, 26 Feb 2026 18:26:20 +0000 Dmitry Ilvokhin <d@ilvokhin.com> wrote:
Nit. Why don't you keep the indentation?
My impression based on below output is that mm code prefer indenting
__acquires().
$ git grep __acquires mm
mm/compaction.c:__acquires(&zone->_lock)
mm/compaction.c:__acquires(&lruvec->lr... | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Thu, 26 Feb 2026 16:45:54 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, 26 Feb 2026 18:26:21 +0000 Dmitry Ilvokhin <d@ilvokhin.com> wrote:
Acked-by: SeongJae Park <sj@kernel.org>
Thanks,
SJ
[...] | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Thu, 26 Feb 2026 16:49:23 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, 26 Feb 2026 16:38:55 -0800
SeongJae Park <sj@kernel.org> wrote:
Hmm, why is this an issue?
I know this is checkpatch and not you complaining about it, but I really
think it's a useless complaint. I can see it better as a do { } while (0)
because it is creating a "function" like feature but can't be inline d... | {
"author": "Steven Rostedt <rostedt@goodmis.org>",
"date": "Thu, 26 Feb 2026 19:53:55 -0500",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, 26 Feb 2026 19:53:55 -0500 Steven Rostedt <rostedt@goodmis.org> wrote:
Makes sense to me, thank you Steve :)
Thanks,
SJ
[...] | {
"author": "SeongJae Park <sj@kernel.org>",
"date": "Thu, 26 Feb 2026 17:01:01 -0800",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, Feb 26, 2026 at 01:31:48PM -0800, Shakeel Butt wrote:
This is a good catch, thank you. I don't think we need EXPORT_SYMBOL()
here. Just verified it locally. I'll remove it in v4. | {
"author": "Dmitry Ilvokhin <d@ilvokhin.com>",
"date": "Fri, 27 Feb 2026 12:39:00 +0000",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, Feb 26, 2026 at 04:31:39PM -0800, SeongJae Park wrote:
Thanks for the feedback, SJ.
Good point. I agree the current name looks too generic. Putting it into
mmzone.h would further overload that header, so renaming zone_lock.h to
mmzone_lock.h seems like the clearest option.
I'll make that change in v4. | {
"author": "Dmitry Ilvokhin <d@ilvokhin.com>",
"date": "Fri, 27 Feb 2026 13:06:00 +0000",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | Add thin wrappers around zone lock acquire/release operations. This
prepares the code for future tracepoint instrumentation without
modifying individual call sites.
Centralizing zone lock operations behind wrappers allows future
instrumentation or debugging hooks to be added without touching
all users.
No functional ... | null | null | null | [PATCH v3 1/5] mm: introduce zone lock wrappers | On Thu, Feb 26, 2026 at 04:45:54PM -0800, SeongJae Park wrote:
Thanks for spotting it, will be fixed in v4. | {
"author": "Dmitry Ilvokhin <d@ilvokhin.com>",
"date": "Fri, 27 Feb 2026 14:46:24 +0000",
"is_openbsd": false,
"thread_id": "aaGuQFaCij5hvw4N@shell.ilvokhin.com.mbox.gz"
} |
lkml_critique | lkml | GPU drivers often need to create their own workqueues for various
reasons. Add the ability to do so.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Changes in v3:
- Switch to builder pattern.
- Drop BH workqueues for now.
- Mark delayed wq change as fix.
- Link to v2: https://lore.kernel.org/r/20251113-create-wo... | null | null | null | [PATCH v3 0/2] Creation of workqueues in Rust | When a workqueue is shut down, delayed work that is pending but not
scheduled does not get properly cleaned up, so it's not safe to use
`enqueue_delayed` on a workqueue that might be destroyed. To fix this,
restricted `enqueue_delayed` to static queues.
Cc: stable@vger.kernel.org
Fixes: 7c098cd5eaae ("workqueue: rust:... | {
"author": "Alice Ryhl <aliceryhl@google.com>",
"date": "Fri, 27 Feb 2026 14:53:20 +0000",
"is_openbsd": false,
"thread_id": "DGPU8USGBKVH.2D5DH6NTL50U2@kernel.org.mbox.gz"
} |
lkml_critique | lkml | GPU drivers often need to create their own workqueues for various
reasons. Add the ability to do so.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Changes in v3:
- Switch to builder pattern.
- Drop BH workqueues for now.
- Mark delayed wq change as fix.
- Link to v2: https://lore.kernel.org/r/20251113-create-wo... | null | null | null | [PATCH v3 0/2] Creation of workqueues in Rust | Creating workqueues is needed by various GPU drivers. Not only does it
give you better control over execution, it also allows devices to ensure
that all tasks have exited before the device is unbound (or similar) by
running the workqueue destructor.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
rust/helpers/wo... | {
"author": "Alice Ryhl <aliceryhl@google.com>",
"date": "Fri, 27 Feb 2026 14:53:21 +0000",
"is_openbsd": false,
"thread_id": "DGPU8USGBKVH.2D5DH6NTL50U2@kernel.org.mbox.gz"
} |
lkml_critique | lkml | GPU drivers often need to create their own workqueues for various
reasons. Add the ability to do so.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Changes in v3:
- Switch to builder pattern.
- Drop BH workqueues for now.
- Mark delayed wq change as fix.
- Link to v2: https://lore.kernel.org/r/20251113-create-wo... | null | null | null | [PATCH v3 0/2] Creation of workqueues in Rust | On Fri Feb 27, 2026 at 3:53 PM CET, Alice Ryhl wrote:
:(
Reviewed-by: Danilo Krummrich <dakr@kernel.org>
We should probably add a FIXME comment pointing out that this should be fixed in
the C code.
Maybe also link your approach? | {
"author": "\"Danilo Krummrich\" <dakr@kernel.org>",
"date": "Fri, 27 Feb 2026 16:10:11 +0100",
"is_openbsd": false,
"thread_id": "DGPU8USGBKVH.2D5DH6NTL50U2@kernel.org.mbox.gz"
} |
lkml_critique | lkml | GPU drivers often need to create their own workqueues for various
reasons. Add the ability to do so.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
Changes in v3:
- Switch to builder pattern.
- Drop BH workqueues for now.
- Mark delayed wq change as fix.
- Link to v2: https://lore.kernel.org/r/20251113-create-wo... | null | null | null | [PATCH v3 0/2] Creation of workqueues in Rust | On Fri Feb 27, 2026 at 3:53 PM CET, Alice Ryhl wrote:
Should we just mention the default value?
The workqueue code prints a warning for max_active > WQ_MAX_ACTIVE. Maybe use
debug_assert()?
It's also a bit unfortunate that alloc_ordered_workqueue() becomes
.max_active(1).
At the same time having a separate ordere... | {
"author": "\"Danilo Krummrich\" <dakr@kernel.org>",
"date": "Fri, 27 Feb 2026 16:30:59 +0100",
"is_openbsd": false,
"thread_id": "DGPU8USGBKVH.2D5DH6NTL50U2@kernel.org.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
This tree fails (more than usual) the powerpc allyesconfig build.
Changes since 20140225:
The mvebu tree gained a conflict against the arm-soc tree.
The powerpc tree still had its build failure.
The libata tree gained a build failure so I used the version from
next-20140225.
The mfd-lj tree still had its ... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Wed, 26 Feb 2014 19:47:38 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | On Wed, 26 Feb 2014 19:47:38 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
^^^^^
That was just wrong :-)
Those were yesterday's figures, today's actually:
Non-merge commits (relative to Linus' tree): 4690
4620 files changed, 177782 insertions(+), 100723 deletion... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Wed, 26 Feb 2014 19:50:50 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
Changes since 20150225:
The drm-intel tree gained a conflict against the drm-intel-fixes tree.
The clk tree gained a build failure so I used the version from
next-20150225.
Non-merge commits (relative to Linus' tree): 1558
1217 files changed, 31765 insertions(+), 30907 deletions(-)
-----------------------... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 26 Feb 2015 14:40:42 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
Changes since 20160225:
The sunxi tree gained conflicts against Linus' and the arm-soc trees.
The net-next tree gained a conflict against the net tree.
The tip tree gained conflicts against the arm64 tree.
The aio tree still had a build failure so I used the version from
next-20160111.
The akpm-current tr... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Fri, 26 Feb 2016 17:37:42 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
Changes since 20180223:
New tree: leaks
The bpf-next tree gained a conflict against the bpf tree.
The kvms390 tree gained a conflict against the nds32 tree.
The percpu tree gained a build failure for which I applied a patch.
The akpm-current tree gained a conflict against the metag tree and a
build failur... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Mon, 26 Feb 2018 16:35:22 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
Changes since 20190225:
The mmc-fixes tree gained a build failure for which I reverted a commit.
The hwmon-staging tree gained a build failure for which I reverted a commit.
The tip tree gained a conflict against the kbuild tree.
The slave-dma tree gained a conflict against Linus' tree.
Non-merge commits ... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Tue, 26 Feb 2019 19:08:59 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
Changes since 20200225:
Removed tree: kasan-bitops (finished with)
The hwmon-fixes tree gained a build failure for which I reverted a commit.
The amlogic tree still had its build failure so I used a supplied patch.
The rdma tree gained a build failure for which I applied a fix.
The regulator tree gained a... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Wed, 26 Feb 2020 15:34:29 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
Please do not add any changes destined for v5.13 to your linux-next
included branches until after v5.12-rc1 has been released.
Changes since 20210225:
Non-merge commits (relative to Linus' tree): 1023
1094 files changed, 34665 insertions(+), 13023 deletions(-)
----------------------------------------------... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Fri, 26 Feb 2021 14:05:37 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
Changes since 20240223:
The mm-nonmm-stable tree gained a conflict against the risc-v-fixes tree.
The perf tree still had its build failure so I removed the object tree
and rebuilt it which worked.
The fuse tree gained a conflict against Linus' tree.
The vfs-brauner tree gained conflictis against the bcach... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Mon, 26 Feb 2024 17:55:09 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
Changes since 20250225:
The mm tree gained a build failure for which I applied a patch.
The drm-xe tree gained a conflict against the drm-intel tree.
The devicetree tree gained a conflict against Linus' tree.
Non-merge commits (relative to Linus' tree): 5854
6515 files changed, 328931 insertions(+), 12517... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Wed, 26 Feb 2025 16:31:40 +1100",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | Hi all,
Changes since 20260225:
We now do a rustfmtcheck build after each x86_64 allmodconfig.
The net-next tree acquired a conflict with the net tree.
The net-next tree acquired a conflict with the origin tree.
Non-merge commits (relative to Linus' tree): 2264
2557 files changed, 203760 insertions(+), 33660 dele... | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Thu, 26 Feb 2026 14:20:52 +0000",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Hi all,
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git.
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was ... | null | null | null | linux-next: Tree for Feb 26 | On Thu, Feb 26, 2026 at 02:20:52PM +0000, Mark Brown wrote:
I meant to CC you yesterday to let you know about the additional rust
checks - I'll add other checks one at a time. | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Fri, 27 Feb 2026 15:03:07 +0000",
"is_openbsd": false,
"thread_id": "759447c5-a2bd-445f-a245-8772f9ea1316@sirena.org.uk.mbox.gz"
} |
lkml_critique | lkml | Add ASPEED_RESET_VIDEO reset definition to the ast2600-clock binding
header. It is required for proper reset control of the video on the
AST2600 SoC for aspeed-video driver.
Fixes: e83f8dd668ea ("media: aspeed: Fix dram hang at res-change")
Signed-off-by: Haiyue Wang <haiyuewa@163.com>
---
v2:
- Fix checkpatch.pl wa... | null | null | null | [PATCH v2 1/2] dt-bindings: clock: ast2600: Add reset definition for video | The aspeed video (be compatible for ast2400, ast2500, ast2600) now needs
the reset DTS handle specified, otherwise it will fail to load:
[ 4.809494] aspeed-video 1e700000.video: irq 57
[ 4.809977] aspeed-video 1e700000.video: Unable to get reset
[ 4.810341] aspeed-video 1e700000.video: probe with driver aspee... | {
"author": "Haiyue Wang <haiyuewa@163.com>",
"date": "Fri, 27 Feb 2026 23:13:15 +0800",
"is_openbsd": false,
"thread_id": "20260227151602.829-1-haiyuewa@163.com.mbox.gz"
} |
lkml_critique | lkml | From: Conor Dooley <conor.dooley@microchip.com>
In 2024 I sent a v7 of adding support for the GPIOs on PolarFire SoC,
which relied on an irqchip driver for a mux sitting between the GPIO
controllers and the main interrupt controller on the chip:
https://lore.kernel.org/all/20240723-flatworm-cornflake-8023212f6584@wend... | null | null | null | [RFC v11 0/4] PolarFire SoC GPIO interrupt support | From: Conor Dooley <conor.dooley@microchip.com>
Add support for interrupts to the PolarFire SoC GPIO driver. Each GPIO
has an independent interrupt that is wired to an interrupt mux that sits
between the controllers and the PLIC. The SoC has more GPIO lines than
connections from the mux to the PLIC, so some GPIOs must... | {
"author": "Conor Dooley <conor@kernel.org>",
"date": "Fri, 27 Feb 2026 14:52:27 +0000",
"is_openbsd": false,
"thread_id": "20260227-manhunt-sixtieth-a7928d5b7e98@spud.mbox.gz"
} |
lkml_critique | lkml | From: Conor Dooley <conor.dooley@microchip.com>
In 2024 I sent a v7 of adding support for the GPIOs on PolarFire SoC,
which relied on an irqchip driver for a mux sitting between the GPIO
controllers and the main interrupt controller on the chip:
https://lore.kernel.org/all/20240723-flatworm-cornflake-8023212f6584@wend... | null | null | null | [RFC v11 0/4] PolarFire SoC GPIO interrupt support | From: Conor Dooley <conor.dooley@microchip.com>
On PolarFire SoC there are more GPIO interrupts than there are interrupt
lines available on the PLIC, and a runtime configurable mux is used to
decide which interrupts are assigned direct connections to the PLIC &
which are relegated to sharing a line.
Signed-off-by: Co... | {
"author": "Conor Dooley <conor@kernel.org>",
"date": "Fri, 27 Feb 2026 14:52:28 +0000",
"is_openbsd": false,
"thread_id": "20260227-manhunt-sixtieth-a7928d5b7e98@spud.mbox.gz"
} |
lkml_critique | lkml | From: Conor Dooley <conor.dooley@microchip.com>
In 2024 I sent a v7 of adding support for the GPIOs on PolarFire SoC,
which relied on an irqchip driver for a mux sitting between the GPIO
controllers and the main interrupt controller on the chip:
https://lore.kernel.org/all/20240723-flatworm-cornflake-8023212f6584@wend... | null | null | null | [RFC v11 0/4] PolarFire SoC GPIO interrupt support | From: Conor Dooley <conor.dooley@microchip.com>
On PolarFire SoC there are more GPIO interrupts than there are interrupt
lines available on the PLIC, and a runtime configurable mux is used to
decide which interrupts are assigned direct connections to the PLIC &
which are relegated to sharing a line.
Add a driver so t... | {
"author": "Conor Dooley <conor@kernel.org>",
"date": "Fri, 27 Feb 2026 14:52:29 +0000",
"is_openbsd": false,
"thread_id": "20260227-manhunt-sixtieth-a7928d5b7e98@spud.mbox.gz"
} |
lkml_critique | lkml | From: Conor Dooley <conor.dooley@microchip.com>
In 2024 I sent a v7 of adding support for the GPIOs on PolarFire SoC,
which relied on an irqchip driver for a mux sitting between the GPIO
controllers and the main interrupt controller on the chip:
https://lore.kernel.org/all/20240723-flatworm-cornflake-8023212f6584@wend... | null | null | null | [RFC v11 0/4] PolarFire SoC GPIO interrupt support | From: Conor Dooley <conor.dooley@microchip.com>
There are 3 GPIO controllers on this SoC, of which:
- GPIO controller 0 has 14 GPIOs
- GPIO controller 1 has 24 GPIOs
- GPIO controller 2 has 32 GPIOs
All GPIOs are capable of generating interrupts, for a total of 70.
There are only 41 IRQs available however, so a confi... | {
"author": "Conor Dooley <conor@kernel.org>",
"date": "Fri, 27 Feb 2026 14:52:30 +0000",
"is_openbsd": false,
"thread_id": "20260227-manhunt-sixtieth-a7928d5b7e98@spud.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.