source large_stringclasses 2
values | subject large_stringclasses 112
values | code large_stringclasses 112
values | critique large_stringlengths 61 3.04M ⌀ | metadata dict |
|---|---|---|---|---|
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On 1/27/26 11:21, Jacob Pan wrote:
It's x86 specific:
x86_init.iommu.iommu_init = hv_iommu_init
oh, you are talking about the config option, yeah, I will move
CONFIG_IRQ_REMAP from Kconfig to here.
it could, but by convention all public funcs here are hv_iommu_xxx..
and other reviewers might object... W... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 15:44:37 -0800",
"thread_id": "20260120064230.3602565-1-mrathor@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Fri, Jan 30, 2026 at 02:51:19PM -0800, Mukesh R wrote:
Again, the hypervisor state is not accessible from the kernel core in
L1VH.
In upstream, it does not matter what the work is focused on. The only
thing that matters is that the functionality is merged and available.
Once the code is merged upstream, it become... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 2 Feb 2026 08:20:37 -0800",
"thread_id": "20260120064230.3602565-1-mrathor@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH v0 00/15] PCI passthru on Hyper-V (Part I) | From: Mukesh Rathor <mrathor@linux.microsoft.com>
Implement passthru of PCI devices to unprivileged virtual machines
(VMs) when Linux is running as a privileged VM on Microsoft Hyper-V
hypervisor. This support is made to fit within the workings of VFIO
framework, and any VMM needing to use it must use the VFIO subsyst... | On Fri, Jan 30, 2026 at 02:17:24PM -0800, Mukesh R wrote:
So, are you saying that the hypervisor does not use these pages and only
tracks them? That would make things easier.
However, if we later try to map a GPA that is already mapped, will the
hypervisor return an error?
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 2 Feb 2026 08:30:49 -0800",
"thread_id": "20260120064230.3602565-1-mrathor@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The "qup-memory" interconnect path is optional and may not be defined
in all device trees. Unroll the loop-based ICC path initialization to
allow specific error handling for each path type.
The "qup-core" and "qup-config" paths remain mandatory and will fail
probe if missing, while "qup-memory" is now handled as optio... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:10 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Add a new function geni_icc_set_bw_ab() that allows callers to set
average bandwidth values for all ICC (Interconnect) paths in a single
call. This function takes separate parameters for core, config, and DDR
average bandwidth values and applies them to the respective ICC paths.
This provides a more convenient API for... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:11 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine drivers (I2C, SPI, and SERIAL) currently duplicate
code for initializing shared resources such as clocks and interconnect
paths.
Introduce a new helper API, geni_se_resources_init(), to centralize this
initialization logic, improving modularity and simplifying the probe
function.
Signed-off-by:... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:12 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Currently, core clk is handled individually in protocol drivers like
the I2C driver. Move this clock management to the common clock APIs
(geni_se_clks_on/off) that are already present in the common GENI SE
driver to maintain consistency across all protocol drivers.
Core clk is now properly managed alongside the other ... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:13 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI SE protocol drivers (I2C, SPI, UART) implement similar resource
activation/deactivation sequences independently, leading to code
duplication.
Introduce geni_se_resources_activate()/geni_se_resources_deactivate() to
power on/off resources.The activate function enables ICC, clocks, and TLMM
whereas the deactiva... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:14 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine drivers (I2C, SPI, and SERIAL) currently handle
the attachment of power domains. This often leads to duplicated code
logic across different driver probe functions.
Introduce a new helper API, geni_se_domain_attach(), to centralize
the logic for attaching "power" and "perf" domains to the GENI SE... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:15 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine (SE) drivers (I2C, SPI, and SERIAL) currently
manage performance levels and operating points directly. This resulting
in code duplication across drivers. such as configuring a specific level
or find and apply an OPP based on a clock frequency.
Introduce two new helper APIs, geni_se_set_perf_leve... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:16 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Add DT bindings for the QUP GENI I2C controller on sa8255p platforms.
SA8255p platform abstracts resources such as clocks, interconnect and
GPIO pins configuration in Firmware. SCMI power and perf protocol
are utilized to request resource configurations.
SA8255p platform does not require the Serial Engine (SE) common... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:17 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Moving the serial engine setup to geni_i2c_init() API for a cleaner
probe function and utilizes the PM runtime API to control resources
instead of direct clock-related APIs for better resource management.
Enables reusability of the serial engine initialization like
hibernation and deep sleep features where hardware co... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:18 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Refactor the resource initialization in geni_i2c_probe() by introducing
a new geni_i2c_resources_init() function and utilizing the common
geni_se_resources_init() framework and clock frequency mapping, making the
probe function cleaner.
Acked-by: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Signed-off-by: Pravee... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:19 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | To manage GENI serial engine resources during runtime power management,
drivers currently need to call functions for ICC, clock, and
SE resource operations in both suspend and resume paths, resulting in
code duplication across drivers.
The new geni_se_resources_activate() and geni_se_resources_deactivate()
helper APIs... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:20 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | To avoid repeatedly fetching and checking platform data across various
functions, store the struct of_device_id data directly in the i2c
private structure. This change enhances code maintainability and reduces
redundancy.
Acked-by: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Signed-off-by: Praveen Talari <prave... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:21 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:22 +0530",
"thread_id": "20260202180922.1692428-6-praveen.talari@oss.qualcomm.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": "b2f12140-ee3d-45bc-864e-d51317c83b8d@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": "b2f12140-ee3d-45bc-864e-d51317c83b8d@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": "b2f12140-ee3d-45bc-864e-d51317c83b8d@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": "b2f12140-ee3d-45bc-864e-d51317c83b8d@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": "b2f12140-ee3d-45bc-864e-d51317c83b8d@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": "b2f12140-ee3d-45bc-864e-d51317c83b8d@cherry.de.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Add verify-only public key crypto support for ML-DSA so that the
X.509/PKCS#7 signature verification code, as used by module signing,
amongst other things, can make use of it through the common crypto_sig API.
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
cc: Eric ... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:06 +0000",
"thread_id": "20260202170216.2467036-8-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Calculate the SHA256 hash for blacklisting purposes independently of the
signature hash (which may be something other than SHA256).
This is necessary because when ML-DSA is used, no digest is calculated.
Note that this represents a change of behaviour in that the hash used for
the blacklist check would previously hav... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:07 +0000",
"thread_id": "20260202170216.2467036-8-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Rename ->digest and ->digest_len to ->m and ->m_size to represent the input
to the signature verification algorithm, reflecting that ->digest may no
longer actually *be* a digest.
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
cc: Lukas Wunner <lukas@wunner.de>
cc: ... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:08 +0000",
"thread_id": "20260202170216.2467036-8-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Allow the data to be verified in a PKCS#7 or CMS message to be passed
directly to an asymmetric cipher algorithm (e.g. ML-DSA) if it wants to do
whatever passes for hashing/digestion itself. The normal digestion of the
data is then skipped as that would be ignored unless another signed info in
the message has some oth... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:09 +0000",
"thread_id": "20260202170216.2467036-8-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Add support for ML-DSA keys and signatures to the CMS/PKCS#7 and X.509
implementations. ML-DSA-44, -65 and -87 are all supported. For X.509
certificates, the TBSCertificate is required to be signed directly; for
CMS, direct signing of the data is preferred, though use of SHA512 (and
only that) as an intermediate hash... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:10 +0000",
"thread_id": "20260202170216.2467036-8-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Allow ML-DSA module signing to be enabled.
Note that OpenSSL's CMS_*() function suite does not, as of OpenSSL-3.6,
support the use of CMS_NOATTR with ML-DSA, so the prohibition against using
signedAttrs with module signing has to be removed. The selected digest
then applies only to the algorithm used to calculate the... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:11 +0000",
"thread_id": "20260202170216.2467036-8-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Allow the rejection of authenticatedAttributes in PKCS#7 (signedAttrs in
CMS) to be waived in the kernel config for ML-DSA when used for module
signing. This reflects the issue that openssl < 4.0 cannot do this and
openssl-4 has not yet been released.
This does not permit RSA, ECDSA or ECRDSA to be so waived (behavio... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:12 +0000",
"thread_id": "20260202170216.2467036-8-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v2 0/4] Improve Hyper-V memory deposit error handling | This series extends the MSHV driver to properly handle additional
memory-related error codes from the Microsoft Hypervisor by depositing
memory pages when needed.
Currently, when the hypervisor returns HV_STATUS_INSUFFICIENT_MEMORY
during partition creation, the driver calls hv_call_deposit_pages() to
provide the nece... | Replace direct comparisons of hv_result(status) against
HV_STATUS_INSUFFICIENT_MEMORY with a new hv_result_needs_memory() helper
function.
This improves code readability and provides a consistent and extendable
interface for checking out-of-memory conditions in hypercall results.
No functional changes intended.
Signe... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 02 Feb 2026 17:58:57 +0000",
"thread_id": "177005513775.120041.4894134857240187839.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net.mbox.gz"
} |
lkml | [PATCH v2 0/4] Improve Hyper-V memory deposit error handling | This series extends the MSHV driver to properly handle additional
memory-related error codes from the Microsoft Hypervisor by depositing
memory pages when needed.
Currently, when the hypervisor returns HV_STATUS_INSUFFICIENT_MEMORY
during partition creation, the driver calls hv_call_deposit_pages() to
provide the nece... | Introduce hv_deposit_memory_node() and hv_deposit_memory() helper
functions to handle memory deposition with proper error handling.
The new hv_deposit_memory_node() function takes the hypervisor status
as a parameter and validates it before depositing pages. It checks for
HV_STATUS_INSUFFICIENT_MEMORY specifically and... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 02 Feb 2026 17:59:03 +0000",
"thread_id": "177005513775.120041.4894134857240187839.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net.mbox.gz"
} |
lkml | [PATCH v2 0/4] Improve Hyper-V memory deposit error handling | This series extends the MSHV driver to properly handle additional
memory-related error codes from the Microsoft Hypervisor by depositing
memory pages when needed.
Currently, when the hypervisor returns HV_STATUS_INSUFFICIENT_MEMORY
during partition creation, the driver calls hv_call_deposit_pages() to
provide the nece... | The HV_STATUS_INSUFFICIENT_CONTIGUOUS_MEMORY status indicates that the
hypervisor lacks sufficient contiguous memory for its internal allocations.
When this status is encountered, allocate and deposit
HV_MAX_CONTIGUOUS_ALLOCATION_PAGES contiguous pages to the hypervisor.
HV_MAX_CONTIGUOUS_ALLOCATION_PAGES is defined i... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 02 Feb 2026 17:59:09 +0000",
"thread_id": "177005513775.120041.4894134857240187839.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net.mbox.gz"
} |
lkml | [PATCH v2 0/4] Improve Hyper-V memory deposit error handling | This series extends the MSHV driver to properly handle additional
memory-related error codes from the Microsoft Hypervisor by depositing
memory pages when needed.
Currently, when the hypervisor returns HV_STATUS_INSUFFICIENT_MEMORY
during partition creation, the driver calls hv_call_deposit_pages() to
provide the nece... | When creating guest partition objects, the hypervisor may fail to
allocate root partition pages and return an insufficient memory status.
In this case, deposit memory using the root partition ID instead.
Note: This error should never occur in a guest of L1VH partition context.
Signed-off-by: Stanislav Kinsburskii <sk... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 02 Feb 2026 17:59:14 +0000",
"thread_id": "177005513775.120041.4894134857240187839.stgit@skinsburskii-cloud-desktop.internal.cloudapp.net.mbox.gz"
} |
lkml | [PATCH 0/3] Axiado AX3000 USB Device Controller | Dear maintainers,
This patch series introduces new USB Device Controller driver for Axiado AX3000 SoC and its evaluation board.
The driver integrates with the Linux USB subsystem and follows kernel coding standards.
This initial submission includes:
- Driver implementation under drivers/usb/gadget/udc
- Device tree ... | Add Axiado ax3000-udc (for USB v2.0 ports) and
ax3000-udc-gen3 (for USB v3.0 ports)
compatible string for AX3000 SoC.
Co-developed-by: Krutik Shah <krutikshah@axiado.com>
Signed-off-by: Krutik Shah <krutikshah@axiado.com>
Co-developed-by: Prasad Bolisetty <pbolisetty@axiado.com>
Signed-off-by: Prasad Bolisetty <pbolis... | {
"author": "Vladimir Moravcevic <vmoravcevic@axiado.com>",
"date": "Mon, 02 Feb 2026 05:16:28 -0800",
"thread_id": "202602030223.QlbiPC8d-lkp@intel.com.mbox.gz"
} |
lkml | [PATCH 0/3] Axiado AX3000 USB Device Controller | Dear maintainers,
This patch series introduces new USB Device Controller driver for Axiado AX3000 SoC and its evaluation board.
The driver integrates with the Linux USB subsystem and follows kernel coding standards.
This initial submission includes:
- Driver implementation under drivers/usb/gadget/udc
- Device tree ... | Add the MAINTAINERS entries for the Axiado USB Device Controller.
Co-developed-by: Krutik Shah <krutikshah@axiado.com>
Signed-off-by: Krutik Shah <krutikshah@axiado.com>
Co-developed-by: Prasad Bolisetty <pbolisetty@axiado.com>
Signed-off-by: Prasad Bolisetty <pbolisetty@axiado.com>
Signed-off-by: Vladimir Moravcevic ... | {
"author": "Vladimir Moravcevic <vmoravcevic@axiado.com>",
"date": "Mon, 02 Feb 2026 05:16:30 -0800",
"thread_id": "202602030223.QlbiPC8d-lkp@intel.com.mbox.gz"
} |
lkml | [PATCH 0/3] Axiado AX3000 USB Device Controller | Dear maintainers,
This patch series introduces new USB Device Controller driver for Axiado AX3000 SoC and its evaluation board.
The driver integrates with the Linux USB subsystem and follows kernel coding standards.
This initial submission includes:
- Driver implementation under drivers/usb/gadget/udc
- Device tree ... | Add Corigine USB IP Driver for Axiado AX3000 SoC's
USB peripheral (USB 2.0/3.0).
The driver is based on the Corigine USB IP core with
Axiado-specific enhancements including VBUS detection and USB link
stability fixes.
The driver supports both USB 2.0 High-Speed and USB 3.0 SuperSpeed
modes with control, bulk, interrup... | {
"author": "Vladimir Moravcevic <vmoravcevic@axiado.com>",
"date": "Mon, 02 Feb 2026 05:16:29 -0800",
"thread_id": "202602030223.QlbiPC8d-lkp@intel.com.mbox.gz"
} |
lkml | [PATCH 0/3] Axiado AX3000 USB Device Controller | Dear maintainers,
This patch series introduces new USB Device Controller driver for Axiado AX3000 SoC and its evaluation board.
The driver integrates with the Linux USB subsystem and follows kernel coding standards.
This initial submission includes:
- Driver implementation under drivers/usb/gadget/udc
- Device tree ... | Hi Vladimir,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 63804fed149a6750ffd28610c5c1c98cce6bd377]
url: https://github.com/intel-lab-lkp/linux/commits/Vladimir-Moravcevic/dt-bindings-usb-axiado-ax3000-udc-Add-Axiado-UDC/20260202-211951
base: 63804fed149a6750ffd28610c5c1c9... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Tue, 3 Feb 2026 01:37:05 +0800",
"thread_id": "202602030223.QlbiPC8d-lkp@intel.com.mbox.gz"
} |
lkml | [PATCH 0/3] Axiado AX3000 USB Device Controller | Dear maintainers,
This patch series introduces new USB Device Controller driver for Axiado AX3000 SoC and its evaluation board.
The driver integrates with the Linux USB subsystem and follows kernel coding standards.
This initial submission includes:
- Driver implementation under drivers/usb/gadget/udc
- Device tree ... | Hi Vladimir,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 63804fed149a6750ffd28610c5c1c98cce6bd377]
url: https://github.com/intel-lab-lkp/linux/commits/Vladimir-Moravcevic/dt-bindings-usb-axiado-ax3000-udc-Add-Axiado-UDC/20260202-211951
base: 63804fed149a6750ffd28610c5c1c9... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Tue, 3 Feb 2026 02:20:11 +0800",
"thread_id": "202602030223.QlbiPC8d-lkp@intel.com.mbox.gz"
} |
lkml | [PATCH 0/2] Add HPET NMI Watchdog support | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | To implement an HPET based NMI watchdog, the HPET code will need to
reconfigure an IOAPIC pin to NMI mode. Add a function that allows driver
code to configure an IOAPIC pin for NMI delivery mode.
(Disclaimer: Some of this code was written with the help of Kiro, an AI
coding assistant)
Signed-off-by: Alexander Graf <g... | {
"author": "Alexander Graf <graf@amazon.com>",
"date": "Mon, 2 Feb 2026 17:43:15 +0000",
"thread_id": "e38c5244-9e8f-467c-b3aa-8098f288a2c3@amazon.com.mbox.gz"
} |
lkml | [PATCH 0/2] Add HPET NMI Watchdog support | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | {
"author": "Alexander Graf <graf@amazon.com>",
"date": "Mon, 2 Feb 2026 17:48:01 +0000",
"thread_id": "e38c5244-9e8f-467c-b3aa-8098f288a2c3@amazon.com.mbox.gz"
} |
lkml | [PATCH 0/2] Add HPET NMI Watchdog support | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | On 02.02.26 18:43, Alexander Graf wrote:
Sorry for the resend. I caught an issue while sending out the series,
hit ctrl-c before thinking and suddenly had a half sent series. Discard
this one. Happy review on the real, full one :)
Alex
Amazon Web Services Development Center Germany GmbH
Tamara-Danz-Str. 13
10... | {
"author": "Alexander Graf <graf@amazon.com>",
"date": "Mon, 2 Feb 2026 18:49:13 +0100",
"thread_id": "e38c5244-9e8f-467c-b3aa-8098f288a2c3@amazon.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Add verify-only public key crypto support for ML-DSA so that the
X.509/PKCS#7 signature verification code, as used by module signing,
amongst other things, can make use of it through the common crypto_sig API.
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
cc: Eric ... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:06 +0000",
"thread_id": "20260202170216.2467036-7-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Calculate the SHA256 hash for blacklisting purposes independently of the
signature hash (which may be something other than SHA256).
This is necessary because when ML-DSA is used, no digest is calculated.
Note that this represents a change of behaviour in that the hash used for
the blacklist check would previously hav... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:07 +0000",
"thread_id": "20260202170216.2467036-7-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Rename ->digest and ->digest_len to ->m and ->m_size to represent the input
to the signature verification algorithm, reflecting that ->digest may no
longer actually *be* a digest.
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
cc: Lukas Wunner <lukas@wunner.de>
cc: ... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:08 +0000",
"thread_id": "20260202170216.2467036-7-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Allow the data to be verified in a PKCS#7 or CMS message to be passed
directly to an asymmetric cipher algorithm (e.g. ML-DSA) if it wants to do
whatever passes for hashing/digestion itself. The normal digestion of the
data is then skipped as that would be ignored unless another signed info in
the message has some oth... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:09 +0000",
"thread_id": "20260202170216.2467036-7-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Add support for ML-DSA keys and signatures to the CMS/PKCS#7 and X.509
implementations. ML-DSA-44, -65 and -87 are all supported. For X.509
certificates, the TBSCertificate is required to be signed directly; for
CMS, direct signing of the data is preferred, though use of SHA512 (and
only that) as an intermediate hash... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:10 +0000",
"thread_id": "20260202170216.2467036-7-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Allow ML-DSA module signing to be enabled.
Note that OpenSSL's CMS_*() function suite does not, as of OpenSSL-3.6,
support the use of CMS_NOATTR with ML-DSA, so the prohibition against using
signedAttrs with module signing has to be removed. The selected digest
then applies only to the algorithm used to calculate the... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:11 +0000",
"thread_id": "20260202170216.2467036-7-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Allow the rejection of authenticatedAttributes in PKCS#7 (signedAttrs in
CMS) to be waived in the kernel config for ML-DSA when used for module
signing. This reflects the issue that openssl < 4.0 cannot do this and
openssl-4 has not yet been released.
This does not permit RSA, ECDSA or ECRDSA to be so waived (behavio... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:12 +0000",
"thread_id": "20260202170216.2467036-7-dhowells@redhat.com.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": "3fbc5be7ae889501dc8562376aa38707f0e8bdd4.camel@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": "3fbc5be7ae889501dc8562376aa38707f0e8bdd4.camel@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": "3fbc5be7ae889501dc8562376aa38707f0e8bdd4.camel@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": "3fbc5be7ae889501dc8562376aa38707f0e8bdd4.camel@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": "3fbc5be7ae889501dc8562376aa38707f0e8bdd4.camel@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": "3fbc5be7ae889501dc8562376aa38707f0e8bdd4.camel@posteo.de.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.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": "20260129212510.967611-1-dmatlack@google.com.mbox.gz"
} |
lkml | [PATCH v2 net] net: phy: change devlink flag to AUTOREMOVE_SUPPLIER for non-SFP PHYs | For the shared MDIO bus use case, multiple MACs will share the same MDIO
bus. Therefore, these MACs all depend on this MDIO bus. If this shared
MDIO bus is removed, all the PHY devices attached to this MDIO bus will
also be removed. Consequently, the MAC driver should not access the PHY
device, otherwise, it will lead ... | Hi Wei,
On 02/02/2026 06:45, Wei Fang wrote:
I gave that patch a test, with the following cases :
- On Macchiatobin (we have PHYs that share an mdiobus).
When unbinding a PHY, the MAC dissapears as well :
#before :
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
... | {
"author": "Maxime Chevallier <maxime.chevallier@bootlin.com>",
"date": "Mon, 2 Feb 2026 12:10:41 +0100",
"thread_id": "aYDmPUN5Z-eRWW2K@shell.armlinux.org.uk.mbox.gz"
} |
lkml | [PATCH v2 net] net: phy: change devlink flag to AUTOREMOVE_SUPPLIER for non-SFP PHYs | For the shared MDIO bus use case, multiple MACs will share the same MDIO
bus. Therefore, these MACs all depend on this MDIO bus. If this shared
MDIO bus is removed, all the PHY devices attached to this MDIO bus will
also be removed. Consequently, the MAC driver should not access the PHY
device, otherwise, it will lead ... | On Mon, Feb 02, 2026 at 12:10:41PM +0100, Maxime Chevallier wrote:
Correct, this is why these band-aids are harmful. One "device" can
correspond with *multiple* network interfaces, and the loss of one
PHY can have a *very* detrimental effect.
Consider the case where root-NFS is being used, and removing a PHY
on anoth... | {
"author": "\"Russell King (Oracle)\" <linux@armlinux.org.uk>",
"date": "Mon, 2 Feb 2026 14:25:09 +0000",
"thread_id": "aYDmPUN5Z-eRWW2K@shell.armlinux.org.uk.mbox.gz"
} |
lkml | [PATCH v2 net] net: phy: change devlink flag to AUTOREMOVE_SUPPLIER for non-SFP PHYs | For the shared MDIO bus use case, multiple MACs will share the same MDIO
bus. Therefore, these MACs all depend on this MDIO bus. If this shared
MDIO bus is removed, all the PHY devices attached to this MDIO bus will
also be removed. Consequently, the MAC driver should not access the PHY
device, otherwise, it will lead ... | On 02/02/2026 15:25, Russell King (Oracle) wrote:
That's what I've been seeing. I unbound one PHY, it took out 3 netdevs
and I don't have log regarding "why". I guess there's devlink debug
knobs for that, but not enabled by default it seems.
However, we seem to have the issue even without this patch.
On MCBin, if I ... | {
"author": "Maxime Chevallier <maxime.chevallier@bootlin.com>",
"date": "Mon, 2 Feb 2026 18:38:48 +0100",
"thread_id": "aYDmPUN5Z-eRWW2K@shell.armlinux.org.uk.mbox.gz"
} |
lkml | [PATCH v2 net] net: phy: change devlink flag to AUTOREMOVE_SUPPLIER for non-SFP PHYs | For the shared MDIO bus use case, multiple MACs will share the same MDIO
bus. Therefore, these MACs all depend on this MDIO bus. If this shared
MDIO bus is removed, all the PHY devices attached to this MDIO bus will
also be removed. Consequently, the MAC driver should not access the PHY
device, otherwise, it will lead ... | On Mon, Feb 02, 2026 at 06:38:48PM +0100, Maxime Chevallier wrote:
See what I said above. "One "device" can correspond with *multiple*
network interfaces".
On Armada 8040, one network "device" has multiple ports - they all
share the same packet infrastructure. Each port is a separate
interface in the kernel.
Consequ... | {
"author": "\"Russell King (Oracle)\" <linux@armlinux.org.uk>",
"date": "Mon, 2 Feb 2026 18:00:29 +0000",
"thread_id": "aYDmPUN5Z-eRWW2K@shell.armlinux.org.uk.mbox.gz"
} |
lkml | [PATCH 0/2] Add HPET NMI Watchdog support | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | To implement an HPET based NMI watchdog, the HPET code will need to
reconfigure an IOAPIC pin to NMI mode. Add a function that allows driver
code to configure an IOAPIC pin for NMI delivery mode.
(Disclaimer: Some of this code was written with the help of Kiro, an AI
coding assistant)
Signed-off-by: Alexander Graf <g... | {
"author": "Alexander Graf <graf@amazon.com>",
"date": "Mon, 2 Feb 2026 17:43:15 +0000",
"thread_id": "20260202174803.66640-2-graf@amazon.com.mbox.gz"
} |
lkml | [PATCH 0/2] Add HPET NMI Watchdog support | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | To implement an HPET based NMI watchdog, the HPET code will need to
reconfigure an IOAPIC pin to NMI mode. Add a function that allows driver
code to configure an IOAPIC pin for NMI delivery mode.
The caller can choose whether to invoke NMIs on the BSP or broadcast on
all CPUs in the system.
(Disclaimer: Some of this ... | {
"author": "Alexander Graf <graf@amazon.com>",
"date": "Mon, 2 Feb 2026 17:48:02 +0000",
"thread_id": "20260202174803.66640-2-graf@amazon.com.mbox.gz"
} |
lkml | [PATCH 0/2] Add HPET NMI Watchdog support | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | The traditional NMI watchdog timer uses performance counters to trigger
periodic NMIs. But performance counters are a scarce resource that are
best used for actual performance counting. However, the HPET is another
timer source on most modern x86 systems that can inject NMI interrupts.
Add support for using HPET timer... | {
"author": "Alexander Graf <graf@amazon.com>",
"date": "Mon, 2 Feb 2026 17:48:03 +0000",
"thread_id": "20260202174803.66640-2-graf@amazon.com.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | The index value is already a copy of the maple state so there is no need
to set it again.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/maple_tree.c b/lib/maple_tree.c
index 9ab42821ee2dc..1e780427c04a0 100644
--- ... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:09 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Use RCU_INIT_POINTER to initialize an rcu pointer to an initial value
since there are no readers within the tree being created during
duplication. There is no risk of readers seeing the initialized or
uninitialized value until after the synchronization call in
mas_dup_buld().
Signed-off-by: Liam R. Howlett <Liam.Howl... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:06 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Height is not used locally in the function, so call the height argument
closer to where it is passed in the next level.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/lib/maple_tree.c b/lib/maple_tree.c
index a... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:13 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Move the loop over the tree levels to its own function.
No intended functional changes.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 108 +++++++++++++++++++++++++----------------------
1 file changed, 58 insertions(+), 50 deletions(-)
diff --git a/lib/maple_tree.c b/lib/maple_tre... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:07 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Copy the contents of mas_spanning_rebalance() into
mas_wr_spanning_rebalance(), in preparation of removing initial big node
use.
No functional changes intended.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 20 +++++++++++++++++++-
1 file changed, 19 insertions(+), 1 deletion(-)
di... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:10 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Isolate big node to use in its own function.
No functional changes intended.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 44 ++++++++++++++++++++++++++------------------
1 file changed, 26 insertions(+), 18 deletions(-)
diff --git a/lib/maple_tree.c b/lib/maple_tree.c
index 70ad4... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:08 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Moving the maple_subtree_state is necessary for future cleanups and is
only set up in mas_wr_spanning_rebalance() but never used.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 41 +++++++++++++++++++++--------------------
1 file changed, 21 insertions(+), 20 deletions(-)
diff --git ... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:14 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | The end_piv will be needed in the next patch set and has not been set
correctly in this code path. Correct the oversight before using it.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/maple_tree.c b/lib/maple_tree.c
index c5bb341... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:15 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Just copy the code and replace count with height. This is done to avoid
affecting other code paths into mas_spanning_rebalance_loop() for the
next change.
No functional change intended.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 108 ++++++++++++++++++++++++++++++++++++++++++++++... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:18 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Introduce an internal-memory only node type called maple_copy to
facilitate internal copy operations. Use it in mas_spanning_rebalance()
for just the leaf nodes. Initially, the maple_copy node is used to
configure the source nodes and copy the data into the big_node.
The maple_copy contains a list of source entries ... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:16 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Now that the spanning rebalance is small, fully inline it in
mas_wr_spanning_store().
No functional change.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 38 +++++++++++++++-----------------------
1 file changed, 15 insertions(+), 23 deletions(-)
diff --git a/lib/maple_tree.c b/lib... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:23 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
lkml | [PATCH v3 00/30] maple_tree: Replace big node with maple copy | The big node struct was created for simplicity of splitting,
rebalancing, and spanning store operations by using a copy buffer to
create the data necessary prior to breaking it up into 256B nodes.
Certain operations were rather tricky due to the restriction of keeping
NULL entries together and never at the end of a nod... | Add a helper to do what is needed when the maple copy node contains a
new root node. This is useful for future commits and is
self-documenting code.
Signed-off-by: Liam R. Howlett <Liam.Howlett@oracle.com>
---
lib/maple_tree.c | 70 ++++++++++++++++++++++++++----------------------
1 file changed, 38 insertions(+), 3... | {
"author": "\"Liam R. Howlett\" <Liam.Howlett@oracle.com>",
"date": "Fri, 30 Jan 2026 15:59:26 -0500",
"thread_id": "20260202103154.ad1aa05611c79d21b070a861@linux-foundation.org.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.