source large_stringclasses 2
values | subject large_stringclasses 112
values | code large_stringclasses 112
values | critique large_stringlengths 61 3.04M ⌀ | metadata dict |
|---|---|---|---|---|
lkml | [syzbot] [hfs?] kernel BUG in may_open (3) | Hello,
syzbot found the following issue on:
HEAD commit: b6151c4e60e5 Merge tag 'erofs-for-6.19-rc5-fixes' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d45922580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
dashboard link: https://... | On Mon, 12 Jan 2026 at 10:27, 'Christian Brauner' via syzkaller-bugs
<syzkaller-bugs@googlegroups.com> wrote:
+hfsplus maintainers
#syz set subsystems: hfs | {
"author": "Dmitry Vyukov <dvyukov@google.com>",
"date": "Mon, 12 Jan 2026 11:35:54 +0100",
"thread_id": "de541759cfa4d216e342bf15b07f93a21f46498b.camel@ibm.com.mbox.gz"
} |
lkml | [syzbot] [hfs?] kernel BUG in may_open (3) | Hello,
syzbot found the following issue on:
HEAD commit: b6151c4e60e5 Merge tag 'erofs-for-6.19-rc5-fixes' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d45922580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
dashboard link: https://... | On Mon, 12 Jan 2026 18:39:23 +0900, Tetsuo Handa wrote:
Applied to the vfs-7.0.misc branch of the vfs/vfs.git tree.
Patches in the vfs-7.0.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it... | {
"author": "Christian Brauner <brauner@kernel.org>",
"date": "Tue, 13 Jan 2026 09:55:33 +0100",
"thread_id": "de541759cfa4d216e342bf15b07f93a21f46498b.camel@ibm.com.mbox.gz"
} |
lkml | [syzbot] [hfs?] kernel BUG in may_open (3) | Hello,
syzbot found the following issue on:
HEAD commit: b6151c4e60e5 Merge tag 'erofs-for-6.19-rc5-fixes' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d45922580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
dashboard link: https://... | On Tue, 2026-01-13 at 09:55 +0100, Christian Brauner wrote:
I've already taken this patch into HFS/HFS+ tree. :) Should I remove it from the
tree?
Thanks,
Slava. | {
"author": "Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>",
"date": "Tue, 13 Jan 2026 17:18:40 +0000",
"thread_id": "de541759cfa4d216e342bf15b07f93a21f46498b.camel@ibm.com.mbox.gz"
} |
lkml | [syzbot] [hfs?] kernel BUG in may_open (3) | Hello,
syzbot found the following issue on:
HEAD commit: b6151c4e60e5 Merge tag 'erofs-for-6.19-rc5-fixes' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d45922580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
dashboard link: https://... | On Tue, Jan 13, 2026 at 05:18:40PM +0000, Viacheslav Dubeyko wrote:
No, I'll drop it. | {
"author": "Christian Brauner <brauner@kernel.org>",
"date": "Wed, 14 Jan 2026 17:05:04 +0100",
"thread_id": "de541759cfa4d216e342bf15b07f93a21f46498b.camel@ibm.com.mbox.gz"
} |
lkml | [syzbot] [hfs?] kernel BUG in may_open (3) | Hello,
syzbot found the following issue on:
HEAD commit: b6151c4e60e5 Merge tag 'erofs-for-6.19-rc5-fixes' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d45922580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
dashboard link: https://... | On 2026/01/15 1:05, Christian Brauner wrote:
I still can't see this patch in linux-next tree. What is happening? | {
"author": "Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>",
"date": "Sun, 1 Feb 2026 13:03:36 +0900",
"thread_id": "de541759cfa4d216e342bf15b07f93a21f46498b.camel@ibm.com.mbox.gz"
} |
lkml | [syzbot] [hfs?] kernel BUG in may_open (3) | Hello,
syzbot found the following issue on:
HEAD commit: b6151c4e60e5 Merge tag 'erofs-for-6.19-rc5-fixes' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d45922580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b058fb1d7dbe6b1
dashboard link: https://... | On Sun, 2026-02-01 at 13:03 +0900, Tetsuo Handa wrote:
The patch in HFS/HFS+ tree. I will send it in pull request for 6.20-rc1.
Thanks,
Slava. | {
"author": "Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>",
"date": "Mon, 2 Feb 2026 17:30:56 +0000",
"thread_id": "de541759cfa4d216e342bf15b07f93a21f46498b.camel@ibm.com.mbox.gz"
} |
lkml | [PATCH 0/2] arm64: dts: rockchip: fix Ethernet PHY on Theobroma
PX30 devices | This removes the reliance on the bootloader setting up the Ethernet PHY
for the Linux kernel to be able to use Ethernet.
This is due to the HW default of the PHY reset line being active and the
MDIO auto-detection mechanism not controlling a PHY's reset line such
that we need to hardcode the PHY ID in the compatible p... | From: Quentin Schulz <quentin.schulz@cherry.de>
When not passing the PHY ID with an ethernet-phy-idX.Y compatible
property, the MDIO bus will attempt to auto-detect the PHY by reading
its registers and then probing the appropriate driver. For this to work,
the PHY needs to be in a working state.
Unfortunately, the ne... | {
"author": "Quentin Schulz <foss+kernel@0leil.net>",
"date": "Mon, 02 Feb 2026 11:27:26 +0100",
"thread_id": "20260202-px30-eth-phy-v1-0-ef365be64922@cherry.de.mbox.gz"
} |
lkml | [PATCH 0/2] arm64: dts: rockchip: fix Ethernet PHY on Theobroma
PX30 devices | This removes the reliance on the bootloader setting up the Ethernet PHY
for the Linux kernel to be able to use Ethernet.
This is due to the HW default of the PHY reset line being active and the
MDIO auto-detection mechanism not controlling a PHY's reset line such
that we need to hardcode the PHY ID in the compatible p... | From: Quentin Schulz <quentin.schulz@cherry.de>
When not passing the PHY ID with an ethernet-phy-idX.Y compatible
property, the MDIO bus will attempt to auto-detect the PHY by reading
its registers and then probing the appropriate driver. For this to work,
the PHY needs to be in a working state.
Unfortunately, the ne... | {
"author": "Quentin Schulz <foss+kernel@0leil.net>",
"date": "Mon, 02 Feb 2026 11:27:25 +0100",
"thread_id": "20260202-px30-eth-phy-v1-0-ef365be64922@cherry.de.mbox.gz"
} |
lkml | [PATCH 0/2] arm64: dts: rockchip: fix Ethernet PHY on Theobroma
PX30 devices | This removes the reliance on the bootloader setting up the Ethernet PHY
for the Linux kernel to be able to use Ethernet.
This is due to the HW default of the PHY reset line being active and the
MDIO auto-detection mechanism not controlling a PHY's reset line such
that we need to hardcode the PHY ID in the compatible p... | On Mon, Feb 02, 2026 at 11:27:25AM +0100, Quentin Schulz wrote:
What is the justification for stable?
Andrew | {
"author": "Andrew Lunn <andrew@lunn.ch>",
"date": "Mon, 2 Feb 2026 14:52:18 +0100",
"thread_id": "20260202-px30-eth-phy-v1-0-ef365be64922@cherry.de.mbox.gz"
} |
lkml | [PATCH 0/2] arm64: dts: rockchip: fix Ethernet PHY on Theobroma
PX30 devices | This removes the reliance on the bootloader setting up the Ethernet PHY
for the Linux kernel to be able to use Ethernet.
This is due to the HW default of the PHY reset line being active and the
MDIO auto-detection mechanism not controlling a PHY's reset line such
that we need to hardcode the PHY ID in the compatible p... | Hi Andrew,
On 2/2/26 2:52 PM, Andrew Lunn wrote:
Bootloader without network stack = no network in Linux.
Cheers,
Quentin | {
"author": "Quentin Schulz <quentin.schulz@cherry.de>",
"date": "Mon, 2 Feb 2026 15:02:08 +0100",
"thread_id": "20260202-px30-eth-phy-v1-0-ef365be64922@cherry.de.mbox.gz"
} |
lkml | [PATCH 0/2] arm64: dts: rockchip: fix Ethernet PHY on Theobroma
PX30 devices | This removes the reliance on the bootloader setting up the Ethernet PHY
for the Linux kernel to be able to use Ethernet.
This is due to the HW default of the PHY reset line being active and the
MDIO auto-detection mechanism not controlling a PHY's reset line such
that we need to hardcode the PHY ID in the compatible p... | On Mon, Feb 02, 2026 at 03:02:08PM +0100, Quentin Schulz wrote:
I can see this multiple ways....
Changing the bootloader introduces a regression. Hence you cannot
change the bootloader.
I personally also don't like boot loaders with basic functionality
missing. Why cripple the bootloader by removing the network stac... | {
"author": "Andrew Lunn <andrew@lunn.ch>",
"date": "Mon, 2 Feb 2026 15:55:56 +0100",
"thread_id": "20260202-px30-eth-phy-v1-0-ef365be64922@cherry.de.mbox.gz"
} |
lkml | [PATCH 0/2] arm64: dts: rockchip: fix Ethernet PHY on Theobroma
PX30 devices | This removes the reliance on the bootloader setting up the Ethernet PHY
for the Linux kernel to be able to use Ethernet.
This is due to the HW default of the PHY reset line being active and the
MDIO auto-detection mechanism not controlling a PHY's reset line such
that we need to hardcode the PHY ID in the compatible p... | On 2/2/26 3:55 PM, Andrew Lunn wrote:
Ringneck is a SoM (system-on-module), I don't control what the user
wants to do with it. So they may never have the networking stack enabled
in the first place (I provide a U-Boot defconfig to use with the devkit,
but I don't control what they do with it; it's also supported up... | {
"author": "Quentin Schulz <quentin.schulz@cherry.de>",
"date": "Mon, 2 Feb 2026 17:31:58 +0100",
"thread_id": "20260202-px30-eth-phy-v1-0-ef365be64922@cherry.de.mbox.gz"
} |
lkml | [PATCH 5.15.y 1/3] wifi: cfg80211: add a work abstraction with special semantics | From: Johannes Berg <johannes.berg@intel.com>
[ Upstream commit a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 ]
Add a work abstraction at the cfg80211 level that will always
hold the wiphy_lock() for any work executed and therefore also
can be canceled safely (without waiting) while holding that.
This improves on what we ... | From: Johannes Berg <johannes.berg@intel.com>
[ Upstream commit 16114496d684a3df4ce09f7c6b7557a8b2922795 ]
We'll need this later to convert other works that might
be cancelled from here, so convert this one first.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Hanne-Lotta Mäenpää <hannelotta@g... | {
"author": "=?UTF-8?q?Hanne-Lotta=20M=C3=A4enp=C3=A4=C3=A4?= <hannelotta@gmail.com>",
"date": "Mon, 2 Feb 2026 18:50:37 +0200",
"thread_id": "20260202165038.215693-2-hannelotta@gmail.com.mbox.gz"
} |
lkml | [PATCH 5.15.y 1/3] wifi: cfg80211: add a work abstraction with special semantics | From: Johannes Berg <johannes.berg@intel.com>
[ Upstream commit a3ee4dc84c4e9d14cb34dad095fd678127aca5b6 ]
Add a work abstraction at the cfg80211 level that will always
hold the wiphy_lock() for any work executed and therefore also
can be canceled safely (without waiting) while holding that.
This improves on what we ... | From: Johannes Berg <johannes.berg@intel.com>
[ Upstream commit 777b26002b73127e81643d9286fadf3d41e0e477 ]
Again, to have the wiphy locked for it.
Reviewed-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
[ Summary of conflict resolutions:
- In mlme.c, move... | {
"author": "=?UTF-8?q?Hanne-Lotta=20M=C3=A4enp=C3=A4=C3=A4?= <hannelotta@gmail.com>",
"date": "Mon, 2 Feb 2026 18:50:38 +0200",
"thread_id": "20260202165038.215693-2-hannelotta@gmail.com.mbox.gz"
} |
lkml | [PATCH v2 0/2] ARM64 support for doorbell and intercept SINTs | From: "Anirudh Rayabharam (Microsoft)" <anirudh@anirudhrb.com>
On x86, the HYPERVISOR_CALLBACK_VECTOR is used to receive synthetic
interrupts (SINTs) from the hypervisor for doorbells and intercepts.
There is no such vector reserved for arm64.
On arm64, the INTID for SINTs should be in the SGI or PPI range. The
hyper... | From: Anirudh Rayabharam (Microsoft) <anirudh@anirudhrb.com>
Rename mshv_synic_init() to mshv_synic_cpu_init() and
mshv_synic_cleanup() to mshv_synic_cpu_exit() to better reflect that
these functions handle per-cpu synic setup and teardown.
Use mshv_synic_init/cleanup() to perform init/cleanup that is not per-cpu.
Mo... | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Mon, 2 Feb 2026 18:27:05 +0000",
"thread_id": "20260202182706.648192-3-anirudh@anirudhrb.com.mbox.gz"
} |
lkml | [PATCH v2 0/2] ARM64 support for doorbell and intercept SINTs | From: "Anirudh Rayabharam (Microsoft)" <anirudh@anirudhrb.com>
On x86, the HYPERVISOR_CALLBACK_VECTOR is used to receive synthetic
interrupts (SINTs) from the hypervisor for doorbells and intercepts.
There is no such vector reserved for arm64.
On arm64, the INTID for SINTs should be in the SGI or PPI range. The
hyper... | From: Anirudh Rayabharam (Microsoft) <anirudh@anirudhrb.com>
On x86, the HYPERVISOR_CALLBACK_VECTOR is used to receive synthetic
interrupts (SINTs) from the hypervisor for doorbells and intercepts.
There is no such vector reserved for arm64.
On arm64, the INTID for SINTs should be in the SGI or PPI range. The
hypervi... | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Mon, 2 Feb 2026 18:27:06 +0000",
"thread_id": "20260202182706.648192-3-anirudh@anirudhrb.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Export liveupdate_enabled(), liveupdate_register_file_handler(), and
liveupdate_unregister_file_handler(). All of these will be used by
vfio-pci in a subsequent commit, which can be built as a module.
Signed-off-by: David Matlack <dmatlack@google.com>
---
kernel/liveupdate/luo_core.c | 1 +
kernel/liveupdate/luo_file... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:48 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Inherit bus numbers from the previous kernel during a Live Update when
one or more PCI devices are being preserved. This is necessary so that
preserved devices can DMA through the IOMMU during a Live Update
(changing bus numbers would break IOMMU translation).
Signed-off-by: David Matlack <dmatlack@google.com>
---
dr... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:50 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Add an API to enable the PCI subsystem to track all devices that are
preserved across a Live Update, including both incoming devices (passed
from the previous kernel) and outgoing devices (passed to the next
kernel).
Use PCI segment number and BDF to keep track of devices across Live
Update. This means the kernel must... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:49 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | From: Vipin Sharma <vipinsh@google.com>
Register a live update file handler for vfio-pci device files. Add stub
implementations of all required callbacks so that registration does not
fail (i.e. to avoid breaking git-bisect).
This file handler will be extended in subsequent commits to enable a
device bound to vfio-pc... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:51 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | From: Vipin Sharma <vipinsh@google.com>
Implement the live update file handler callbacks to preserve a vfio-pci
device across a Live Update. Subsequent commits will enable userspace to
then retrieve this file after the Live Update.
Live Update support is scoped only to cdev files (i.e. not
VFIO_GROUP_GET_DEVICE_FD fi... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:52 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | From: Vipin Sharma <vipinsh@google.com>
Enable userspace to retrieve preserved VFIO device files from VFIO after
a Live Update by implementing the retrieve() and finish() file handler
callbacks.
Use an anonymous inode when creating the file, since the retrieved
device file is not opened through any particular cdev in... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:53 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Notify the PCI subsystem about devices vfio-pci is preserving across
Live Update by registering the vfio-pci liveupdate file handler with the
PCI subsystem's FLB handler.
Notably this will ensure that devices preserved through vfio-pci will
have their PCI bus numbers preserved across Live Update, allowing VFIO
to use ... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:54 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Enforce that files for incoming (preserved by previous kernel) VFIO
devices are retrieved via LIVEUPDATE_SESSION_RETRIEVE_FD rather than by
opening the corresponding VFIO character device or via
VFIO_GROUP_GET_DEVICE_FD.
Both of these methods would result in VFIO initializing the device
without access to the preserved... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:55 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Stash a pointer to a device's incoming Live Updated state in struct
vfio_pci_core_device. This will enable subsequent commits to use the
preserved state when initializing the device.
To enable VFIO to safely access this pointer during device enablement,
require that the device is fully enabled before returning true fr... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:56 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | From: Vipin Sharma <vipinsh@google.com>
Do not reset the device when a Live Update preserved vfio-pci device is
retrieved and first enabled. vfio_pci_liveupdate_freeze() guarantees the
device is reset prior to Live Update, so there's no reason to reset it
again after Live Update.
Since VFIO normally uses the initial ... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:57 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Add documentation for preserving VFIO device files across a Live Update,
as well as some generic file preservation documentation. This
documentation will be extended in the future as new types of files are
supported and new dependency/ordering requirements are added.
Signed-off-by: David Matlack <dmatlack@google.com>
... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:58 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | From: Vipin Sharma <vipinsh@google.com>
Move luo_test_utils.[ch] into a lib/ directory and pull the rules to
build them out into a separate make script. This will enable these
utilities to be also built by and used within other selftests (such as
VFIO) in subsequent commits.
No functional change intended.
Signed-off... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:24:59 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | From: Vipin Sharma <vipinsh@google.com>
Add helper functions to preserve and retrieve file descriptors from an
LUO session. These will be used be used in subsequent commits to
preserve FDs other than memfd.
No functional change intended.
Signed-off-by: Vipin Sharma <vipinsh@google.com>
Co-developed-by: David Matlack... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:00 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Add a selftest to exercise preserving a various VFIO files through
/dev/liveupdate. Ensure that VFIO cdev device files can be preserved and
everything else (group-based device files, group files, and container
files) all fail.
Signed-off-by: David Matlack <dmatlack@google.com>
---
tools/testing/selftests/vfio/Makefil... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:03 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | From: Vipin Sharma <vipinsh@google.com>
Import and build liveupdate selftest library in VFIO selftests.
It allows to use liveupdate ioctls in VFIO selftests
Signed-off-by: Vipin Sharma <vipinsh@google.com>
Signed-off-by: David Matlack <dmatlack@google.com>
---
tools/testing/selftests/vfio/Makefile | 11 ++++++++---
... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:01 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Add Makefile support for TEST_GEN_PROGS_EXTENDED targets. These tests
are not run by default.
TEST_GEN_PROGS_EXTENDED will be used for Live Update selftests in
subsequent commits. These selftests must be run manually because they
require the user/runner to perform additional actions, such as kexec,
during the test.
S... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:02 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | From: Vipin Sharma <vipinsh@google.com>
Use the given VFIO cdev FD to initialize vfio_pci_device in VFIO
selftests. Add the assertion to make sure that passed cdev FD is not
used with legacy VFIO APIs. If VFIO cdev FD is provided then do not open
the device instead use the FD for any interaction with the device.
This... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:04 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Expose the list of iommu_modes to enable tests that want to iterate
through all possible iommu modes.
Signed-off-by: David Matlack <dmatlack@google.com>
---
tools/testing/selftests/vfio/lib/include/libvfio/iommu.h | 2 ++
tools/testing/selftests/vfio/lib/iommu.c | 4 +++-
2 files changed, 5 insertions... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:06 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Expose a few low-level helper routings for setting up vfio_pci_device
structs. These routines will be used in a subsequent commit to assert
that VFIO_GROUP_GET_DEVICE_FD fails under certain conditions.
Signed-off-by: David Matlack <dmatlack@google.com>
---
.../lib/include/libvfio/vfio_pci_device.h | 5 +++
.../s... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:07 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Verify that opening a VFIO device through its cdev file and via
VFIO_GROUP_GET_DEVICE_FD both fail with -EBUSY if the device was
preserved across a Live Update. When a device file is preserve across a
Live Update, the file must be retrieved from /dev/liveupdate, not from
VFIO directly.
Signed-off-by: David Matlack <dm... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:08 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Add a long-running DMA memcpy operation to
vfio_pci_liveupdate_kexec_test so that the device attempts to perform
DMAs continuously during the Live Update.
At this point iommufd preservation is not supported and bus mastering is
not kept enabled on the device during across the kexec, so most of these
DMAs will be dropp... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:09 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | From: Vipin Sharma <vipinsh@google.com>
Add a selftest to exercise preserving a vfio-pci device across a Live
Update. For now the test is extremely simple and just verifies that the
device file can be preserved and retrieved. In the future this test will
be extended to verify more parts about device preservation as th... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 21:25:05 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Hi David,
On Thu, 29 Jan 2026 21:24:57 +0000
David Matlack <dmatlack@google.com> wrote:
Just wondering what happened to skipping the bus master clearing. I
understand this version does not preserve the device itself yet; I’m
just curious whether there were specific difficulties that led to
dropping the earlier patch ... | {
"author": "Jacob Pan <jacob.pan@linux.microsoft.com>",
"date": "Thu, 29 Jan 2026 14:21:58 -0800",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | On 2026-01-29 02:21 PM, Jacob Pan wrote:
Hi Jacob,
There's several places where bus master gets cleared that we need to
eventually eliminate to fully preserve the device.
1. vfio_pci_liveupdate_freeze() clears it during shutdown when it
restores vdev->pci_saved_state.
2. pci_device_shutdown() clears it during... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Thu, 29 Jan 2026 22:33:13 +0000",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | Hi David,
On Thu, 29 Jan 2026 22:33:13 +0000
David Matlack <dmatlack@google.com> wrote:
I was just asking about (3) and trying to understand the asymmetric
handling compared to reset. I don’t have a strong preference since this
is temporary—thanks for the explanation.
I’ve been testing my noiommu cdev patches on to... | {
"author": "Jacob Pan <jacob.pan@linux.microsoft.com>",
"date": "Thu, 29 Jan 2026 16:31:50 -0800",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | 在 2026/1/29 13:24, David Matlack 写道:
Can the above 2 functions support the virtual devices? For example,
bonding, veth, iSWAP and RXE.
These virtual devices do not have BDF. As such, I am not sure if your
patches take these virtual devices in to account.
Thanks a lot.
Zhu Yanjun
--
Best Regards,
Yanjun.Zhu | {
"author": "Zhu Yanjun <yanjun.zhu@linux.dev>",
"date": "Sat, 31 Jan 2026 22:38:18 -0800",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 00/22] vfio/pci: Base Live Update support for VFIO device files | This series can be found on GitHub:
https://github.com/dmatlack/linux/tree/liveupdate/vfio/cdev/v2
This series adds the base support to preserve a VFIO device file across
a Live Update. "Base support" means that this allows userspace to
safely preserve a VFIO device file with LIVEUPDATE_SESSION_PRESERVE_FD
and retr... | On Sat, Jan 31, 2026 at 10:38 PM Zhu Yanjun <yanjun.zhu@linux.dev> wrote:
No this patch series only supports PCI devices, since those are the
only devices so far we've needed to support.
I am not familiar with any of the devices that you mentioned. If they
are virtual then does that mean it's all just software? In th... | {
"author": "David Matlack <dmatlack@google.com>",
"date": "Mon, 2 Feb 2026 10:14:56 -0800",
"thread_id": "CALzav=d1ZrHrWd-HhZJ8aY6aqxkBcLoet_5+-LL1mOakVTj6Ww@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | Currently hrtimer_interrupt() runs expired timers, which can re-arm
themselves, after which it computes the next expiration time and
re-programs the hardware.
However, things like HRTICK, a highres timer driving preemption,
cannot re-arm itself at the point of running, since the next task has
not been determined yet. ... | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Wed, 21 Jan 2026 17:20:15 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | Hi!
At long last a new version of the hrtick rework! The previous version had a
mysterious deadlock which has been resolved. So far (weeks) the 0-day robot has
not found more issues with these patches.
These patches aim to reduce the hrtick overhead to such an extent that it can
be default enabled. Decoupling the pre... | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Wed, 21 Jan 2026 17:20:10 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | Upon schedule() HRTICK will cancel the current timer, pick the next
task and reprogram the timer. When schedule() consistently triggers
due to blocking conditions instead of the timer, this leads to endless
reprogramming without ever firing.
Mitigate this with a new hrtimer mode: fuzzy (not really happy with
that name... | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Wed, 21 Jan 2026 17:20:13 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | Rework hrtimer_interrupt() such that reprogramming is split out into
an independent function at the end of the interrupt.
This prepares for reprogramming getting delayed beyond the end of
hrtimer_interrupt().
Notably, this changes the hang handling to always wait 100ms instead
of trying to keep it proportional to the... | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Wed, 21 Jan 2026 17:20:14 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | The nominal duration for an EEVDF task to run is until its deadline.
At which point the deadline is moved ahead and a new task selection is
done.
Try and predict the time 'lost' to higher scheduling classes. Since
this is an estimate, the timer can be both early or late. In case it
is early task_tick_fair() will take ... | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Wed, 21 Jan 2026 17:20:11 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | ... for generic entry architectures. This decouples preemption from
CONFIG_HZ, leaving only the periodic load-balancer and various
accounting things relying on the tick.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/sched/features.h | 5 +++++
1 file changed, 5 insertions(+)
--- a/kernel... | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Wed, 21 Jan 2026 17:20:16 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | Hi Peter,
On Wed, Jan 21, 2026 at 05:20:16PM +0100 Peter Zijlstra wrote:
I maybe be missing something. But the title of this patch
and the above code do not seem to match.
Cheers,
Phil
-- | {
"author": "Phil Auld <pauld@redhat.com>",
"date": "Wed, 21 Jan 2026 17:24:44 -0500",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | Hello,
On 21/01/26 17:20, Peter Zijlstra wrote:
...
Nit.. guess we don't fear overflow since vdelta should be bounded
anyway.
Reviewed-by: Juri Lelli <juri.lelli@redhat.com>
Thanks,
Juri | {
"author": "Juri Lelli <juri.lelli@redhat.com>",
"date": "Thu, 22 Jan 2026 11:53:34 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | Hello,
On 21/01/26 17:20, Peter Zijlstra wrote:
Reviewed-by: Juri Lelli <juri.lelli@redhat.com>
Thanks,
Juri | {
"author": "Juri Lelli <juri.lelli@redhat.com>",
"date": "Thu, 22 Jan 2026 12:00:14 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Wed, Jan 21, 2026 at 05:24:44PM -0500, Phil Auld wrote:
Arguably this should be CONFIG_GENERIC_ENTRY I suppose
You mean it only default enables it for a subset of architectures? | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Thu, 22 Jan 2026 12:40:54 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Thu, Jan 22, 2026 at 12:40:54PM +0100 Peter Zijlstra wrote:
Nope, I mean I can't read... nevermind.
Cheers,
Phil
-- | {
"author": "Phil Auld <pauld@redhat.com>",
"date": "Thu, 22 Jan 2026 07:31:17 -0500",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | Hello,
On 21/01/26 17:20, Peter Zijlstra wrote:
Does the more common (lazier :) 'lazy' work better?
...
Not sure either, but since it's improving things for local already,
maybe it's an acceptable first step?
Reviewed-by: Juri Lelli <juri.lelli@redhat.com>
Thanks,
Juri | {
"author": "Juri Lelli <juri.lelli@redhat.com>",
"date": "Thu, 22 Jan 2026 14:12:28 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Thu, 22 Jan 2026 14:12:28 +0100
Juri Lelli <juri.lelli@redhat.com> wrote:
I don't like either fuzzy or lazy.
Fuzzy makes me think of just random entries (for fuzz testing and such).
Lazy is to postpone things to do things less often.
What about "speculative"? Like branch prediction and such. Where a timer
is e... | {
"author": "Steven Rostedt <rostedt@goodmis.org>",
"date": "Fri, 23 Jan 2026 15:04:50 -0500",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Wed, 21 Jan 2026 17:20:15 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
I'm curious to why you decided to use scoped_guard() here and not just
guard() and not add the extra indentation? The function is small enough
where everything is expected to be protected by the spinlock.
-- Steve | {
"author": "Steven Rostedt <rostedt@goodmis.org>",
"date": "Fri, 23 Jan 2026 15:08:43 -0500",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Fri, Jan 23, 2026 at 03:08:43PM -0500, Steven Rostedt wrote:
Yeah, I'm not entirely sure... its been over 6 months since I wrote this
code :-/ | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Fri, 23 Jan 2026 22:04:33 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Wed, Jan 21 2026 at 17:20, Peter Zijlstra wrote:
Reviewed-by: Thomas Gleixner <tglx@kernel.org> | {
"author": "Thomas Gleixner <tglx@linutronix.de>",
"date": "Mon, 02 Feb 2026 13:28:12 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Wed, Jan 21 2026 at 17:20, Peter Zijlstra wrote:
SHouldn't this be HRTIMER_MODE_REL_PINNED_HARD? I know it's set when
starting the timer, but I had to double check it.
I'd rather say:
Fuzzy requires pinned as the lazy reprogramming only works
for CPU local timers.
Other than that:
Review... | {
"author": "Thomas Gleixner <tglx@linutronix.de>",
"date": "Mon, 02 Feb 2026 15:02:26 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Wed, Jan 21 2026 at 17:20, Peter Zijlstra wrote:
Indeed.
in_hrtirq
Reviewed-by: Thomas Gleixner <tglx@kernel.org> | {
"author": "Thomas Gleixner <tglx@linutronix.de>",
"date": "Mon, 02 Feb 2026 15:05:14 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Wed, Jan 21 2026 at 17:20, Peter Zijlstra wrote:
Two things I'm not convinced that they are handled correctly:
1) Interrupts
After reenabling interrupts and before reaching schedule() an
interrupt comes in and runs soft interrupt processing for a while
on the way back, which delays the up... | {
"author": "Thomas Gleixner <tglx@linutronix.de>",
"date": "Mon, 02 Feb 2026 15:37:13 +0100",
"thread_id": "20260121162010.647043073@infradead.org.mbox.gz"
} |
lkml | [PATCH v2 2/6] hrtimer: Optimize __hrtimer_start_range_ns() | Much like hrtimer_reprogram(), skip programming if the cpu_base is
running the hrtimer interrupt.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
kernel/time/hrtimer.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- a/kernel/time/hrtimer.c
+++ b/kernel/time/hrtimer.c
@@ -1261,6 +1261,14 @@ stat... | On Mon, Feb 02, 2026 at 03:37:13PM +0100, Thomas Gleixner wrote:
So the basic thing looks like:
<USER-MODE>
irqentry_enter()
run_irq_on_irqstack_cond()
if (user_mode() || hardirq_stack_inuse)
irq_enter_rcu();
func_c();
irq_exit_rcu()
__irq_exit_rcu()
invoke_softirq()
irqentr... | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Mon, 2 Feb 2026 17:33:55 +0100",
"thread_id": "20260121162010.647043073@infradead.org.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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@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": "aYDrqVEOwkGfv2JG@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH v11 0/3] rust: leds: add led classdev abstractions | This patch series has previously been contained in
https://lore.kernel.org/rust-for-linux/20251008181027.662616-1-markus.probst@posteo.de/T/#t
which added a rust written led driver for a microcontroller via i2c.
As the reading and writing to the i2c client via the register!
macro has not been implemented yet [1], the ... | Implement the core abstractions needed for led class devices, including:
* `led::LedOps` - the trait for handling leds, including
`brightness_set`, `brightness_get` and `blink_set`
* `led::InitData` - data set for the led class device
* `led::Device` - a safe wrapper around `led_classdev`
Signed-off-by: Markus Pr... | {
"author": "Markus Probst <markus.probst@posteo.de>",
"date": "Mon, 02 Feb 2026 13:52:20 +0000",
"thread_id": "20260202-rust_leds-v11-0-585d1c8be20c@posteo.de.mbox.gz"
} |
lkml | [PATCH v11 0/3] rust: leds: add led classdev abstractions | This patch series has previously been contained in
https://lore.kernel.org/rust-for-linux/20251008181027.662616-1-markus.probst@posteo.de/T/#t
which added a rust written led driver for a microcontroller via i2c.
As the reading and writing to the i2c client via the register!
macro has not been implemented yet [1], the ... | Move code specific to normal led class devices into a separate file and
introduce the `led::Mode` trait to allow for other types of led class
devices in `led::LedOps`.
Signed-off-by: Markus Probst <markus.probst@posteo.de>
---
MAINTAINERS | 1 +
rust/kernel/led.rs | 245 ++++++------------------... | {
"author": "Markus Probst <markus.probst@posteo.de>",
"date": "Mon, 02 Feb 2026 13:52:22 +0000",
"thread_id": "20260202-rust_leds-v11-0-585d1c8be20c@posteo.de.mbox.gz"
} |
lkml | [PATCH v11 0/3] rust: leds: add led classdev abstractions | This patch series has previously been contained in
https://lore.kernel.org/rust-for-linux/20251008181027.662616-1-markus.probst@posteo.de/T/#t
which added a rust written led driver for a microcontroller via i2c.
As the reading and writing to the i2c client via the register!
macro has not been implemented yet [1], the ... | Implement the abstractions needed for multicolor led class devices,
including:
* `led::MultiColor` - the led mode implementation
* `MultiColorSubLed` - a safe wrapper arround `mc_subled`
* `led::MultiColorDevice` - a safe wrapper around `led_classdev_mc`
Signed-off-by: Markus Probst <markus.probst@posteo.de>
---
r... | {
"author": "Markus Probst <markus.probst@posteo.de>",
"date": "Mon, 02 Feb 2026 13:52:25 +0000",
"thread_id": "20260202-rust_leds-v11-0-585d1c8be20c@posteo.de.mbox.gz"
} |
lkml | [PATCH v11 0/3] rust: leds: add led classdev abstractions | This patch series has previously been contained in
https://lore.kernel.org/rust-for-linux/20251008181027.662616-1-markus.probst@posteo.de/T/#t
which added a rust written led driver for a microcontroller via i2c.
As the reading and writing to the i2c client via the register!
macro has not been implemented yet [1], the ... | On Mon Feb 2, 2026 at 1:52 PM GMT, Markus Probst wrote:
It appears to me that while this reflects on the C API, on the Rust side this is
more commonly known as the builder pattern.
I think this should properly be name `led::DeviceBuilder`, as it does more than
what `led_init_data` does on the C side (e.g. initial_bri... | {
"author": "\"Gary Guo\" <gary@garyguo.net>",
"date": "Mon, 02 Feb 2026 15:41:56 +0000",
"thread_id": "20260202-rust_leds-v11-0-585d1c8be20c@posteo.de.mbox.gz"
} |
lkml | [PATCH v11 0/3] rust: leds: add led classdev abstractions | This patch series has previously been contained in
https://lore.kernel.org/rust-for-linux/20251008181027.662616-1-markus.probst@posteo.de/T/#t
which added a rust written led driver for a microcontroller via i2c.
As the reading and writing to the i2c client via the register!
macro has not been implemented yet [1], the ... | On Mon Feb 2, 2026 at 1:52 PM GMT, Markus Probst wrote:
This patch deleted a lot of code that's added in the previous one.
Could you structure it in a way without doing this?
Best,
Gary | {
"author": "\"Gary Guo\" <gary@garyguo.net>",
"date": "Mon, 02 Feb 2026 15:43:37 +0000",
"thread_id": "20260202-rust_leds-v11-0-585d1c8be20c@posteo.de.mbox.gz"
} |
lkml | [PATCH v11 0/3] rust: leds: add led classdev abstractions | This patch series has previously been contained in
https://lore.kernel.org/rust-for-linux/20251008181027.662616-1-markus.probst@posteo.de/T/#t
which added a rust written led driver for a microcontroller via i2c.
As the reading and writing to the i2c client via the register!
macro has not been implemented yet [1], the ... | On Mon, 2026-02-02 at 15:41 +0000, Gary Guo wrote:
With into_raw(), the reference count of fwnode would not decrement if
the registration fails.
Thanks
- Markus Probst | {
"author": "Markus Probst <markus.probst@posteo.de>",
"date": "Mon, 02 Feb 2026 16:53:09 +0000",
"thread_id": "20260202-rust_leds-v11-0-585d1c8be20c@posteo.de.mbox.gz"
} |
lkml | [PATCH/for-next v2 0/2] cgroup/cpuset: Fix partition related locking issues | v2:
- Change patch 1 to use workqueue instead of task run as it is a
per-cpu kthread that performs the cpuset shutdown and bringup work.
- Simplify and streamline some of the code.
After booting the latest cgroup for-next debug kernel with the latest
cgroup changes as well as Federic's "cpuset/isolation: Hono... | The update_isolation_cpumasks() function can be called either directly
from regular cpuset control file write with cpuset_full_lock() called
or via the CPU hotplug path with cpus_write_lock and cpuset_mutex held.
As we are going to enable dynamic update to the nozh_full housekeeping
cpumask (HK_TYPE_KERNEL_NOISE) soon... | {
"author": "Waiman Long <longman@redhat.com>",
"date": "Fri, 30 Jan 2026 10:42:53 -0500",
"thread_id": "20260130154254.1422113-1-longman@redhat.com.mbox.gz"
} |
lkml | [PATCH/for-next v2 0/2] cgroup/cpuset: Fix partition related locking issues | v2:
- Change patch 1 to use workqueue instead of task run as it is a
per-cpu kthread that performs the cpuset shutdown and bringup work.
- Simplify and streamline some of the code.
After booting the latest cgroup for-next debug kernel with the latest
cgroup changes as well as Federic's "cpuset/isolation: Hono... | The current cpuset partition code is able to dynamically update
the sched domains of a running system and the corresponding
HK_TYPE_DOMAIN housekeeping cpumask to perform what is essentally the
"isolcpus=domain,..." boot command line feature at run time.
The housekeeping cpumask update requires flushing a number of di... | {
"author": "Waiman Long <longman@redhat.com>",
"date": "Fri, 30 Jan 2026 10:42:54 -0500",
"thread_id": "20260130154254.1422113-1-longman@redhat.com.mbox.gz"
} |
lkml | [PATCH/for-next v2 0/2] cgroup/cpuset: Fix partition related locking issues | v2:
- Change patch 1 to use workqueue instead of task run as it is a
per-cpu kthread that performs the cpuset shutdown and bringup work.
- Simplify and streamline some of the code.
After booting the latest cgroup for-next debug kernel with the latest
cgroup changes as well as Federic's "cpuset/isolation: Hono... | On 2026/1/30 23:42, Waiman Long wrote:
Can this happen?
cpu0 cpu1
[...]
isolated_cpus_updating = true;
...
// 'full_lock' is not acquired
update_isolation_cpumasks
// exec worker concurrently
isolcpus_workfn
cpuset_full_lock
isolated_cpus_updating = false;
cpuset_full_unlock();
// This r... | {
"author": "Chen Ridong <chenridong@huaweicloud.com>",
"date": "Sat, 31 Jan 2026 08:47:37 +0800",
"thread_id": "20260130154254.1422113-1-longman@redhat.com.mbox.gz"
} |
lkml | [PATCH/for-next v2 0/2] cgroup/cpuset: Fix partition related locking issues | v2:
- Change patch 1 to use workqueue instead of task run as it is a
per-cpu kthread that performs the cpuset shutdown and bringup work.
- Simplify and streamline some of the code.
After booting the latest cgroup for-next debug kernel with the latest
cgroup changes as well as Federic's "cpuset/isolation: Hono... | On 2026/1/30 23:42, Waiman Long wrote:
Adding a global variable makes this difficult to handle, especially in
concurrent scenarios, since we could read it outside of a critical region.
I suggest removing cpuset_locked and adding async_update_isolation_cpumasks
instead, which can indicate to the caller it should call ... | {
"author": "Chen Ridong <chenridong@huaweicloud.com>",
"date": "Sat, 31 Jan 2026 08:58:40 +0800",
"thread_id": "20260130154254.1422113-1-longman@redhat.com.mbox.gz"
} |
lkml | [PATCH/for-next v2 0/2] cgroup/cpuset: Fix partition related locking issues | v2:
- Change patch 1 to use workqueue instead of task run as it is a
per-cpu kthread that performs the cpuset shutdown and bringup work.
- Simplify and streamline some of the code.
After booting the latest cgroup for-next debug kernel with the latest
cgroup changes as well as Federic's "cpuset/isolation: Hono... | On 1/30/26 7:47 PM, Chen Ridong wrote:
Note this statement.
That is not true. Either cpus_read_lock or cpus_write_lock and
cpuset_mutex are held when update_isolation_cpumasks() is called. So
there is mutual exclusion.
Cheers,
Longman | {
"author": "Waiman Long <llong@redhat.com>",
"date": "Fri, 30 Jan 2026 20:06:33 -0500",
"thread_id": "20260130154254.1422113-1-longman@redhat.com.mbox.gz"
} |
lkml | [PATCH/for-next v2 0/2] cgroup/cpuset: Fix partition related locking issues | v2:
- Change patch 1 to use workqueue instead of task run as it is a
per-cpu kthread that performs the cpuset shutdown and bringup work.
- Simplify and streamline some of the code.
After booting the latest cgroup for-next debug kernel with the latest
cgroup changes as well as Federic's "cpuset/isolation: Hono... | On 2026/1/31 9:06, Waiman Long wrote:
Thank you for reminder.
Eh, we currently assume that it can only be called from existing scenarios, so
it's okay for now. But I'm concerned that if we later use
update_isolation_cpumasks without realizing that we need to hold either
cpus_write_lock or (cpus_read_lock && cpuset_m... | {
"author": "Chen Ridong <chenridong@huaweicloud.com>",
"date": "Sat, 31 Jan 2026 09:43:07 +0800",
"thread_id": "20260130154254.1422113-1-longman@redhat.com.mbox.gz"
} |
lkml | [PATCH/for-next v2 0/2] cgroup/cpuset: Fix partition related locking issues | v2:
- Change patch 1 to use workqueue instead of task run as it is a
per-cpu kthread that performs the cpuset shutdown and bringup work.
- Simplify and streamline some of the code.
After booting the latest cgroup for-next debug kernel with the latest
cgroup changes as well as Federic's "cpuset/isolation: Hono... | On 1/30/26 7:58 PM, Chen Ridong wrote:
No, cpuset_locked is always read from or written into inside a critical
section. It is under cpuset_mutex up to this point and then with the
cpuset_top_mutex with the next patch.
The point of this global variable is to distinguish between calling from
CPU hotplug and the other... | {
"author": "Waiman Long <llong@redhat.com>",
"date": "Fri, 30 Jan 2026 20:45:52 -0500",
"thread_id": "20260130154254.1422113-1-longman@redhat.com.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.