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] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 12:18:44 +0200",
"thread_id": "2026020258-very-numbly-b36b@gregkh.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | On Mon, Feb 02, 2026 at 12:18:44PM +0200, Bogdan Sandu wrote:
You resent the same thing again?
confused,
greg k-h | {
"author": "Greg KH <gregkh@linuxfoundation.org>",
"date": "Mon, 2 Feb 2026 11:32:15 +0100",
"thread_id": "2026020258-very-numbly-b36b@gregkh.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | The previous patch has now been separated into four smaller ones, each one fixing a specific type of checkpatch.pl issue.
Bogdan Sandu (4):
media: ipu3: fix alignment
media: ipu3: use tabs
media: ipu3: avoid ending lines with paranthesis
media: ipu3: use BIT()
drivers/staging/media/ipu3/ipu3-css.c | 39 ++++... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:29 +0200",
"thread_id": "2026020258-very-numbly-b36b@gregkh.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Fix alignment with parentheses.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-css.c | 22 +++++++++++-----------
drivers/staging/media/ipu3/ipu3-v4l2.c | 11 +++++------
drivers/staging/media/ipu3/ipu3.c | 4 ++--
3 files changed, 18 insertions(+), 19 deletions(-... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:30 +0200",
"thread_id": "2026020258-very-numbly-b36b@gregkh.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Use tabs instead of spaces.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-css.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/ipu3/ipu3-css.c b/drivers/staging/media/ipu3/ipu3-css.c
index 145501e90..e990eb5b3 100644
--- a/... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:31 +0200",
"thread_id": "2026020258-very-numbly-b36b@gregkh.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Don't end line with paranthesis.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-css.c | 13 +++++--------
drivers/staging/media/ipu3/ipu3.c | 3 +--
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/staging/media/ipu3/ipu3-css.c b/drivers/stagi... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:32 +0200",
"thread_id": "2026020258-very-numbly-b36b@gregkh.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Prefer BIT() macro over manual bitshift.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-mmu.c | 2 +-
drivers/staging/media/ipu3/ipu3-mmu.h | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/ipu3/ipu3-mmu.c b/drivers/staging/me... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:33 +0200",
"thread_id": "2026020258-very-numbly-b36b@gregkh.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Convert the device tree binding documentation for tilcdc
from plain text to DT binding schema.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Signed-off-by: Kory Maincent (TI.com) <kory.maincent@bootlin.com>
---
Change in v3:
- Rename binding file to ti,am33xx-tilcdc.yaml.
- Use generic node n... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:19 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | The tilcdc hardware does not generate VESA-compliant sync signals. It
aligns the vertical sync (VS) on the second edge of the horizontal sync
(HS) instead of the first edge. To compensate for this hardware
behavior, the driver applies a timing adjustment in mode_fixup().
Previously, this adjustment was conditional bas... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:21 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | To maintain backward compatibility while removing the deprecated
tilcdc_panel driver, add a tilcdc_panel_legacy subdriver that converts
the legacy "ti,tilcdc,panel" devicetree binding to the standard
panel-dpi binding at early boot.
The conversion uses an embedded device tree overlay that is applied and
modified durin... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:23 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Mark the ti,tilcdc,panel binding as deprecated in the documentation.
This legacy binding should no longer be used for new designs. Users
should migrate to the standard DRM panel bindings instead.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Signed-off-by: Kory Maincent (TI.com) <kory.maincent@b... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:20 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Migrate CRTC mode configuration to use standard DRM bus flags in
preparation for removing the tilcdc_panel driver and its custom
tilcdc_panel_info structure.
Add support for DRM_BUS_FLAG_PIXDATA_DRIVE_NEGEDGE and
DRM_BUS_FLAG_SYNC_DRIVE_NEGEDGE flags to control pixel clock and sync
signal edge polarity, while maintain... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:22 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | The tilcdc panel subdriver is a legacy, non-standard driver that has been
replaced by the standard panel-dpi driver and panel-simple infrastructure.
With the device tree bindings removed and all in-tree users migrated to
use panel-dpi, this driver no longer has any associated device tree
bindings or users. The panel-d... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:24 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | The tilcdc driver previously used the component framework to bind
external encoder subdrivers (specifically the TDA998x HDMI encoder).
With the removal of these subdrivers in previous commits, the component
framework is no longer needed.
This commit removes all component framework infrastructure including:
- Component... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:25 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Remove the unnecessary #endif/#ifdef CONFIG_DEBUG_FS pair that splits
the debugfs code section. This keeps all debugfs-related code within a
single preprocessor conditional block, improving code readability.
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Kory Maincent (TI.com) <kory.maincent@boo... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:27 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Remove the tilcdc_panel_info structure and its associated helper
function as the structure contains only redundant or unused parameters.
Most panel configuration parameters in tilcdc_panel_info are either:
- Already represented by existing DRM mode flags (invert_pxl_clk,
sync_edge via DRM_BUS_FLAG_*), or
- Set to id... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:26 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | The num_encoders/encoders and num_connectors/connectors arrays in
tilcdc_drm_private are never populated or used by the driver.
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Kory Maincent (TI.com) <kory.maincent@bootlin.com>
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 3 +--
drivers/gpu/drm/tilc... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:28 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Remove the "external_" prefix from encoder and connector members in the
tilcdc driver. These are internal driver structures and the "external"
naming is misleading. The simpler names better reflect that these are
the primary encoder and connector managed by this driver.
Also rename tilcdc_attach_external_device() to t... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:29 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | The tilcdc_external module describes the encoder part of the tilcdc
driver. Rename it to tilcdc_encoder for better clarity and to make
the naming more consistent with DRM subsystem conventions, where
encoder-related files typically use "encoder" in their names.
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Si... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:30 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | The tilcdc driver previously supported a sub-module system where
external display drivers (panels, encoders) could register themselves
through tilcdc_module_init() and be automatically initialized through
a module list. This infrastructure became unused after the component
framework support and panel driver was removed... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:31 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Use the drm_module_platform_driver() helper macro to simplify driver
registration. This macro handles both the platform driver registration
and the drm_firmware_drivers_only() check, making the custom init/exit
functions unnecessary.
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Kory Maincent (... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:32 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Move tilcdc_init/fini functions adjacent to the probe and remove functions
in preparation for cleanup and modernization. This improves readability
for subsequent commits that will refactor these functions.
No functional changes, only code reorganization.
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-o... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:33 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Refactor the driver initialization to use modern DRM managed resource
APIs, simplifying the code.
The tilcdc_init and tilcdc_fini wrapper functions are removed since they
served no purpose after the component framework was eliminated. Their
logic is integrated directly into probe and remove.
Key changes:
- Use devm_d... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:34 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | The DRM core documentation recommends against using dev_private:
"Instead of using this pointer it is recommended that drivers use
embed the struct &drm_device in their larger per-device structure."
This patch refactors the tilcdc driver to follow this recommendation
by embedding struct drm_device within struct tilcdc... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:35 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Convert the tilcdc driver to use DRM managed resources (drmm_* APIs)
to eliminate resource lifetime issues, particularly in probe deferral
scenarios.
This conversion addresses potential use-after-free bugs by ensuring
proper cleanup ordering through the DRM managed resource framework.
The changes include:
- Replace dr... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:36 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Replace drm_of_find_panel_or_bridge() with the newer
devm_drm_of_get_bridge() helper which simplifies the code by:
- Automatically handling both panel and bridge cases internally
- Managing the panel-to-bridge conversion when needed
- Using devres for resource management, eliminating manual cleanup
This removes the ne... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:38 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Replace dev_* logging calls with their DRM equivalents.
This aligns with the DRM subsystem's logging infrastructure and provides
better integration with DRM debugging mechanisms. The drm_* helpers
automatically include device information and integrate with DRM's
debug category filtering.
Reviewed-by: Luca Ceresoli <lu... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:37 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | The tilcdc driver no longer uses the component framework to bind the
tda998x bridge driver. The component bind/unbind operations and the
encoder initialization code are now dead code and can be safely removed.
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Kory Maincent (TI.com) <kory.maincent@b... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:39 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Now that tda998x_create and tda998x_destroy are called only in the probe
function, there is no need for separate functions.
Move the code into the tda998x_probe and tda998x_remove functions.
Rewrite the cleanup path using goto calls in probe and reorder it in the
remove function.
Reviewed-by: Luca Ceresoli <luca.ceres... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:40 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Use directly drm_connector_cleanup in the destroy ops instead of having
a custom function that does nothing more.
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Kory Maincent (TI.com) <kory.maincent@bootlin.com>
---
drivers/gpu/drm/bridge/tda998x_drv.c | 7 +------
1 file changed, 1 insertion(+... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:41 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Add support for the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag to allow display
controller drivers to create their own connectors. This modernizes the
driver to work with the current DRM bridge framework.
The implementation includes:
- Refactoring detection and EDID reading into bridge-usable helpers
- Adding bridge operatio... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:42 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Convert the driver to use the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag when
attaching bridges. This modernizes the driver by delegating connector
creation to the bridge subsystem through drm_bridge_connector_init()
instead of manually searching for connectors created by the bridge.
The custom tilcdc_encoder_find_connector(... | {
"author": "\"Kory Maincent (TI.com)\" <kory.maincent@bootlin.com>",
"date": "Fri, 23 Jan 2026 17:12:43 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | Hi Kory,
On Fri Jan 23, 2026 at 5:12 PM CET, Kory Maincent (TI.com) wrote:
I'm OK with this patch, based on the v4 discussion. I have a question
however, see below.
You are introducing a subtle difference here: while you pass the connector
type to devm_drm_panel_bridge_add_typed(), devm_drm_of_get_bridge() does
not... | {
"author": "\"Luca Ceresoli\" <luca.ceresoli@bootlin.com>",
"date": "Fri, 30 Jan 2026 20:31:11 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | On Fri, 30 Jan 2026 20:31:11 +0100
"Luca Ceresoli" <luca.ceresoli@bootlin.com> wrote:
...
The connector type should be set by the bridge or the panel driver.
https://elixir.bootlin.com/linux/v6.18.6/source/drivers/gpu/drm/bridge/panel.c#L397
* This function is deprecated and should not be used in new drivers. Use... | {
"author": "Kory Maincent <kory.maincent@bootlin.com>",
"date": "Mon, 2 Feb 2026 10:57:17 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v5 00/25] Clean and update tilcdc driver to support
DRM_BRIDGE_ATTACH_NO_CONNECTOR | The starting point for this work was adding support for the HDMI cape:
https://www.seeedstudio.com/Seeed-Studio-BeagleBone-Green-HDMI-Cape.html
This will be sent in a later series.
Initially, Miguel proposed modifying the ite-it66121 bridge to support
the legacy behavior without the DRM_BRIDGE_ATTACH_NO_CONNECTOR flag... | On Mon Feb 2, 2026 at 10:57 AM CET, Kory Maincent wrote:
Ah, right, so it means this patch might cause some regressions due to panel
drivers to be fixed. So it's fine as long as you are ready to handle such
regression, should any happen.
Also other patches did exactly the same, e.g.:
commit 6e1853589ea6 ("drm/lcdi... | {
"author": "\"Luca Ceresoli\" <luca.ceresoli@bootlin.com>",
"date": "Mon, 02 Feb 2026 18:07:45 +0100",
"thread_id": "20260123-feature_tilcdc-v5-0-5a44d2aa3f6f@bootlin.com.mbox.gz"
} |
lkml | [PATCH v4] scripts/x86/intel: Add a script to update the old microcode list | The kernel maintains a table of minimum expected microcode revisions for
Intel CPUs in intel-ucode-defs.h. Systems with microcode older than
these revisions are flagged with X86_BUG_OLD_MICROCODE.
The static list of microcode revisions needs to be updated periodically
in response to releases of the official microcode ... | On 30/01/2026 7:47 pm, Sohil Mehta wrote:
return (val >> bottom) & mask
This is crying out for a small class, and for the use of set()
Try the attached version, which is rather more pythonic.
~Andrew | {
"author": "Andrew Cooper <andrew.cooper3@citrix.com>",
"date": "Fri, 30 Jan 2026 22:00:38 +0000",
"thread_id": "5e3dc792-c5aa-4024-b2a3-32db49da8132@intel.com.mbox.gz"
} |
lkml | [PATCH v4] scripts/x86/intel: Add a script to update the old microcode list | The kernel maintains a table of minimum expected microcode revisions for
Intel CPUs in intel-ucode-defs.h. Systems with microcode older than
these revisions are flagged with X86_BUG_OLD_MICROCODE.
The static list of microcode revisions needs to be updated periodically
in response to releases of the official microcode ... | On 1/30/2026 2:00 PM, Andrew Cooper wrote:
Yup, that is better. Saves an extra step/line.
Thank you for improving the script. It looks cleaner and "pythonic". It
works for my usage with unique ucode files in a single directory.
Dave probably has a use case where he passes multiple directories to the
script. IIUC,... | {
"author": "Sohil Mehta <sohil.mehta@intel.com>",
"date": "Fri, 30 Jan 2026 15:09:35 -0800",
"thread_id": "5e3dc792-c5aa-4024-b2a3-32db49da8132@intel.com.mbox.gz"
} |
lkml | [PATCH v4] scripts/x86/intel: Add a script to update the old microcode list | The kernel maintains a table of minimum expected microcode revisions for
Intel CPUs in intel-ucode-defs.h. Systems with microcode older than
these revisions are flagged with X86_BUG_OLD_MICROCODE.
The static list of microcode revisions needs to be updated periodically
in response to releases of the official microcode ... | On 1/30/26 15:09, Sohil Mehta wrote:
I can't think of a case where I wanted to use multiple directories for a
single run of the script. The only thing I tend to do is switch between
the distr-provided ucode in /lib/firmware and a local clone of the Intel
microcode git repo. So, one or the other, not both at once. | {
"author": "Dave Hansen <dave.hansen@intel.com>",
"date": "Mon, 2 Feb 2026 10:01:10 -0800",
"thread_id": "5e3dc792-c5aa-4024-b2a3-32db49da8132@intel.com.mbox.gz"
} |
lkml | [PATCH] Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" | This reverts commit 7294863a6f01248d72b61d38478978d638641bee.
This commit was erroneously applied again after commit 0ab5d711ec74
("drm/amd: Refactor `amdgpu_aspm` to be evaluated per device")
removed it, leading to very hard to debug crashes, when used with a system with two
AMD GPUs of which only one supports ASPM.... | On 1/31/26 6:24 PM, Bert Karwatzki wrote:
Amazing detective work, thanks so much.
This added the code initially:
cba07cce39ace drm/amd: Check if ASPM is enabled from PCIe subsystem
This effectively removed it:
0ab5d711ec74d drm/amd: Refactor `amdgpu_aspm` to be evaluated per device
This was the accidental re-apply:... | {
"author": "Mario Limonciello <superm1@kernel.org>",
"date": "Mon, 2 Feb 2026 08:25:34 -0600",
"thread_id": "15517fd926161aee77b4df2ffa8bab4bd08eab9a.camel@web.de.mbox.gz"
} |
lkml | [PATCH] Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" | This reverts commit 7294863a6f01248d72b61d38478978d638641bee.
This commit was erroneously applied again after commit 0ab5d711ec74
("drm/amd: Refactor `amdgpu_aspm` to be evaluated per device")
removed it, leading to very hard to debug crashes, when used with a system with two
AMD GPUs of which only one supports ASPM.... | On 2/2/26 15:25, Mario Limonciello wrote:
Reviewed-by: Christian König <christian.koenig@amd.com>
There is just one major question left: Why is disabling ASPM causing problems?
I mean we had tons of problems with ASPM before, but only by accidentally enabling it and never accidentally disabling it.
IIRC we even sug... | {
"author": "=?UTF-8?Q?Christian_K=C3=B6nig?= <christian.koenig@amd.com>",
"date": "Mon, 2 Feb 2026 15:35:31 +0100",
"thread_id": "15517fd926161aee77b4df2ffa8bab4bd08eab9a.camel@web.de.mbox.gz"
} |
lkml | [PATCH] Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" | This reverts commit 7294863a6f01248d72b61d38478978d638641bee.
This commit was erroneously applied again after commit 0ab5d711ec74
("drm/amd: Refactor `amdgpu_aspm` to be evaluated per device")
removed it, leading to very hard to debug crashes, when used with a system with two
AMD GPUs of which only one supports ASPM.... | On 2/2/26 8:35 AM, Christian König wrote:
My theory is that it's a mismatch of PCIe core and AMDGPU. IE if the
PCIe core thinks it's enabled but amdgpu thinks it is disabled can hit
some corner scenarios. | {
"author": "Mario Limonciello <superm1@kernel.org>",
"date": "Mon, 2 Feb 2026 10:11:02 -0600",
"thread_id": "15517fd926161aee77b4df2ffa8bab4bd08eab9a.camel@web.de.mbox.gz"
} |
lkml | [PATCH] Revert "drm/amd: Check if ASPM is enabled from PCIe subsystem" | This reverts commit 7294863a6f01248d72b61d38478978d638641bee.
This commit was erroneously applied again after commit 0ab5d711ec74
("drm/amd: Refactor `amdgpu_aspm` to be evaluated per device")
removed it, leading to very hard to debug crashes, when used with a system with two
AMD GPUs of which only one supports ASPM.... | Am Montag, dem 02.02.2026 um 10:11 -0600 schrieb Mario Limonciello:
That's also my theory. In my case the discrete GPU is probed first
[ 1.652505] [ T194] amdgpu 0000:03:00.0: enabling device (0000 -> 0002)
[ 1.658662] [ T194] amdgpu 0000:03:00.0: amdgpu: initializing kernel modesetting (DIMGREY_CAVEFISH ... | {
"author": "Bert Karwatzki <spasswolf@web.de>",
"date": "Mon, 02 Feb 2026 17:43:31 +0100",
"thread_id": "15517fd926161aee77b4df2ffa8bab4bd08eab9a.camel@web.de.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/23/2026 2:20 PM, Stanislav Kinsburskii wrote:
Reviewed-by: Nuno Das Neves <nunodasneves@linux.microsoft.com> | {
"author": "Nuno Das Neves <nunodasneves@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 16:09:49 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/23/26 14:20, Stanislav Kinsburskii wrote:
Will this affect CRASH kexec? I see few CONFIG_CRASH_DUMP in kexec.c
implying that crash dump might be involved. Or did you test kdump
and it was fine?
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 23 Jan 2026 16:16:33 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Fri, Jan 23, 2026 at 04:16:33PM -0800, Mukesh R wrote:
Yes, it will. Crash kexec depends on normal kexec functionality, so it
will be affected as well.
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Sun, 25 Jan 2026 14:39:26 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Fri, Jan 23, 2026 at 10:20:53PM +0000, Stanislav Kinsburskii wrote:
Someone might want to stop all guest VMs and do a kexec. Which is valid
and would work without any issue for L1VH.
Also, I don't think it is reasonable at all that someone needs to
disable basic kernel functionality such as kexec in order to use o... | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Tue, 27 Jan 2026 00:19:24 +0530",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/25/26 14:39, Stanislav Kinsburskii wrote:
So not sure I understand the reason for this patch. We can just block
kexec if there are any VMs running, right? Doing this would mean any
further developement would be without a ver important and major feature,
right? | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 12:20:09 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Mon, Jan 26, 2026 at 12:20:09PM -0800, Mukesh R wrote:
This is an option. But until it's implemented and merged, a user mshv
driver gets into a situation where kexec is broken in a non-obvious way.
The system may crash at any time after kexec, depending on whether the
new kernel touches the pages deposited to hyper... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 12:43:58 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Tue, Jan 27, 2026 at 12:19:24AM +0530, Anirudh Rayabharam wrote:
No, it won't work and hypervsisor depostied pages won't be withdrawn.
Also, kernel consisntency must no depend on use space behavior.
It's a temporary measure until proper page lifecycle management is
supported in the driver.
Mutual exclusion of th... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 12:46:44 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/26/26 12:43, Stanislav Kinsburskii wrote:
I understand that. But with this we cannot collect core and debug any
crashes. I was thinking there would be a quick way to prohibit kexec
for update via notifier or some other quick hack. Did you already
explore that and didn't find anything, hence this?
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 15:07:18 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Mon, Jan 26, 2026 at 03:07:18PM -0800, Mukesh R wrote:
This quick hack you mention isn't quick in the upstream kernel as there
is no hook to interrupt kexec process except the live update one.
I sent an RFC for that one but given todays conversation details is
won't be accepted as is.
Making mshv mutually exclusive... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 16:21:43 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/26/26 16:21, Stanislav Kinsburskii wrote:
That's the one we want to interrupt and block right? crash kexec
is ok and should be allowed. We can document we don't support kexec
for update for now.
Are you taking about this?
"mshv: Add kexec safety for deposited pages"
Yeah, that could take a long time... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Mon, 26 Jan 2026 17:39:49 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Mon, Jan 26, 2026 at 05:39:49PM -0800, Mukesh R wrote:
Yes.
The trade-off here is between disabling kexec support and having the
kernel crash after kexec in a non-obvious way. This affects both regular
kexec and crash kexec.
It’s a pity we can’t apply a quick hack to disable only regular kexec.
However, since cr... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Tue, 27 Jan 2026 09:47:01 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/27/26 09:47, Stanislav Kinsburskii wrote:
crash kexec on baremetal is not affected, hence disabling that
doesn't make sense as we can't debug crashes then on bm.
Let me think and explore a bit, and if I come up with something, I'll
send a patch here. If nothing, then we can do this as last resort.
Thanks,
-Muke... | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Tue, 27 Jan 2026 11:56:02 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | From: Mukesh R <mrathor@linux.microsoft.com> Sent: Tuesday, January 27, 2026 11:56 AM
Maybe you've already looked at this, but there's a sysctl parameter
kernel.kexec_load_limit_reboot that prevents loading a kexec
kernel for reboot if the value is zero. Separately, there is
kernel.kexec_load_limit_panic that con... | {
"author": "Michael Kelley <mhklinux@outlook.com>",
"date": "Wed, 28 Jan 2026 15:53:04 +0000",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Mon, Jan 26, 2026 at 12:46:44PM -0800, Stanislav Kinsburskii wrote:
All pages that were deposited in the context of a guest partition (i.e.
with the guest partition ID), would be withdrawn when you kill the VMs,
right? What other deposited pages would be left?
Thanks,
Anirudh. | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Wed, 28 Jan 2026 16:16:31 +0000",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Tue, Jan 27, 2026 at 11:56:02AM -0800, Mukesh R wrote:
Bare metal support is not currently relevant, as it is not available.
This is the upstream kernel, and this driver will be accessible to
third-party customers beginning with kernel 6.19 for running their
kernels in Azure L1VH, so consistency is required.
Thank... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Wed, 28 Jan 2026 15:08:30 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Wed, Jan 28, 2026 at 04:16:31PM +0000, Anirudh Rayabharam wrote:
The driver deposits two types of pages: one for the guests (withdrawn
upon gust shutdown) and the other - for the host itself (never
withdrawn).
See hv_call_create_partition, for example: it deposits pages for the
host partition.
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Wed, 28 Jan 2026 15:11:14 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/28/26 07:53, Michael Kelley wrote:
Mmm...eee...weelll... i think i see a much easier way to do this by
just hijacking __kexec_lock. I will resume my normal work tmrw/Fri,
so let me test it out. if it works, will send patch Monday.
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Thu, 29 Jan 2026 18:52:59 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/28/26 15:08, Stanislav Kinsburskii wrote:
Well, without crashdump support, customers will not be running anything
anywhere.
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Thu, 29 Jan 2026 18:59:31 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Wed, Jan 28, 2026 at 03:11:14PM -0800, Stanislav Kinsburskii wrote:
Hmm.. I see. Is it not possible to reclaim this memory in module_exit?
Also, can't we forcefully kill all running partitions in module_exit and
then reclaim memory? Would this help with kernel consistency
irrespective of userspace behavior?
Thanks... | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Fri, 30 Jan 2026 17:11:12 +0000",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Thu, Jan 29, 2026 at 06:59:31PM -0800, Mukesh R wrote:
This is my concern too. I don't think customers will be particularly
happy that kexec doesn't work with our driver.
Thanks,
Anirudh | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Fri, 30 Jan 2026 17:17:52 +0000",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Fri, Jan 30, 2026 at 05:17:52PM +0000, Anirudh Rayabharam wrote:
I wasn’t clear earlier, so let me restate it. Today, kexec is not
supported in L1VH. This is a bug we have not fixed yet. Disabling kexec
is not a long-term solution. But it is better to disable it explicitly
than to have kernel crashes after kexec.
... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 10:41:39 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Fri, Jan 30, 2026 at 05:11:12PM +0000, Anirudh Rayabharam wrote:
It would, but this is sloppy and cannot be a long-term solution.
It is also not reliable. We have no hook to prevent kexec. So if we fail
to kill the guest or reclaim the memory for any reason, the new kernel
may still crash.
There are two long-term... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 10:46:45 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/30/26 10:41, Stanislav Kinsburskii wrote:
I don't think there is disagreement on this. The undesired part is turning
off KEXEC config completely.
Thanks,
-Mukesh | {
"author": "Mukesh R <mrathor@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 11:47:48 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Fri, Jan 30, 2026 at 10:46:45AM -0800, Stanislav Kinsburskii wrote:
Actually guests won't be running by the time we reach our module_exit
function during a kexec. Userspace processes would've been killed by
then.
Also, why is this sloppy? Isn't this what module_exit should be
doing anyway? If someone unloads our m... | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Fri, 30 Jan 2026 20:32:45 +0000",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Fri, Jan 30, 2026 at 11:47:48AM -0800, Mukesh R wrote:
There is no disagreement on this either. If you have a better solution
that can be implemented and merged before next kernel merge window,
please propose it. Otherwise, this patch will remain as is for now.
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 2 Feb 2026 08:43:37 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On 1/24/2026 3:50 AM, Stanislav Kinsburskii wrote:
I have not gone through entire conversation that has happened already on
this, but if you send a next version for this, please change commit msg
and subject to include MSHV_ROOT instead of MSHV, to avoid confusion.
Regards,
Naman | {
"author": "Naman Jain <namjain@linux.microsoft.com>",
"date": "Mon, 2 Feb 2026 22:26:10 +0530",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Fri, Jan 30, 2026 at 08:32:45PM +0000, Anirudh Rayabharam wrote:
No, they will not: "kexec -e" doesn't kill user processes.
We must not rely on OS to do graceful shutdown before doing
kexec.
Kexec does not unload modules, but it doesn't really matter even if it
would.
There are other means to plug into the reboot... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 2 Feb 2026 09:10:00 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH] mshv: Make MSHV mutually exclusive with KEXEC | The MSHV driver deposits kernel-allocated pages to the hypervisor during
runtime and never withdraws them. This creates a fundamental incompatibility
with KEXEC, as these deposited pages remain unavailable to the new kernel
loaded via KEXEC, leading to potential system crashes upon kernel accessing
hypervisor deposited... | On Fri, Jan 30, 2026 at 05:11:12PM +0000, Anirudh Rayabharam wrote:
First, module_exit is not called during kexec. Second, forcefully
killing all partitions during a kexec reboot would be bulky,
error-prone, and slow. It also does not guarantee robust behavior. Too
many things can go wrong, and we could still end up i... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 2 Feb 2026 10:09:38 -0800",
"thread_id": "26bdf7a9-91ea-4236-a5a6-d7f8571ab87b@linux.microsoft.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
./drivers/resctrl/mpam_internal.h: linux/srcu.h is included more than once.
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=27328
Signed-off-by: J... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:28 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | In the test__props_mismatch() kunit test we rely on the struct mpam_props
being packed to ensure memcmp doesn't consider packing. Making it packed
reduces the alignment of the features bitmap and so breaks a requirement
for the use of atomics. As we don't rely on the set/clear of these bits
being atomic, just make them... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:29 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | The MPAMSM_EL1 register determines the MPAM configuration for an SMCU. Add
the register definition.
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Signed-off-by: Ben Horgan <ben.horgan@arm.com>
---
arch/arm64/tools/sysreg | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/tools/sysreg... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:30 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | When kvm enables or disables MPAM traps to EL2 it clears all other bits in
MPAM2_EL2. Notably, it clears the partition ids (PARTIDs) and performance
monitoring groups (PMGs). Avoid changing these bits in anticipation of
adding support for MPAM in the kernel. Otherwise, on a VHE system with the
host running at EL2 wher... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:31 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | The MPAMSM_EL1 controls the MPAM labeling for an SMCU, Streaming Mode
Compute Unit. As there is on MPAM support in kvm, make sure MPAMSM_EL1
accesses trigger an UNDEF.
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Signed-off-by: Ben Horgan <ben.horgan@arm.com>
---
Changes since v2:
Remove paragraph from ... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:32 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
MPAM allows traffic in the SoC to be labeled by the OS, these labels are
used to apply policy in caches and bandwidth regulators, and to monitor
traffic in the SoC. The label is made up of a PARTID and PMG value. The x86
equivalent calls these CLOSID and RMID, but they don't map... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:33 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
Now that the MPAM system registers are expected to have values that change,
reprogram them based on the previous value when a CPU is brought online.
Previously MPAM's 'default PARTID' of 0 was always used for MPAM in
kernel-space as this is the PARTID that hardware guarantees t... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:34 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
Requestors need to populate the MPAM fields for any traffic they send on
the interconnect. For the CPUs these values are taken from the
corresponding MPAMy_ELx register. Each requestor may have a limit on the
largest PARTID or PMG value that can be used. The MPAM driver has to
d... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:35 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
The MPAM system registers will be lost if the CPU is reset during PSCI's
CPU_SUSPEND.
Add a PM notifier to restore them.
mpam_thread_switch(current) can't be used as this won't make any changes if
the in-memory copy says the register already has the correct value. In
reality t... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:36 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | The MPAMSM_EL1 sets the MPAM labels, PMG and PARTID, for loads and stores
generated by a shared SMCU. Disable the traps so the kernel can use it and
set it to the same configuration as the per-EL cpu MPAM configuration.
If an SMCU is not shared with other cpus then it is implementation
defined whether the configuratio... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:37 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
Care must be taken when modifying the PARTID and PMG of a task in any
per-task structure as writing these values may race with the task being
scheduled in, and reading the modified values.
Add helpers to set the task properties, and the CPU default value. These
use WRITE_ONCE(... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:38 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
While we trap the guest's attempts to read/write the MPAM control
registers, the hardware continues to use them. Guest-EL0 uses KVM's
user-space's configuration, as the value is left in the register, and
guest-EL1 uses either the host kernel's configuration, or in the case of
VH... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:39 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | On nVHE systems whether or not MPAM is enabled, EL2 continues to use
partid-0 for hypercalls, even when the host may have configured its kernel
threads to use a different partid. 0 may have been assigned to another
task. Copy the EL1 MPAM register to EL2. This ensures hypercalls use the
same partid as the kernel thread... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:40 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
resctrl has its own data structures to describe its resources. We can't use
these directly as we play tricks with the 'MBA' resource, picking the MPAM
controls or monitors that best apply. We may export the same component as
both L3 and MBA.
Add mpam_resctrl_exports[] as the ar... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:41 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
resctrl documents that the domains appear in numeric order in the schemata
file. This means a little more work is needed when bringing a domain
online.
Add the support for this, using resctrl_find_domain() to find the point to
insert in the list.
Reviewed-by: Jonathan Cameron ... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:42 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
Systems with MPAM support may have a variety of control types at any point
of their system layout. We can only expose certain types of control, and
only if they exist at particular locations.
Start with the well-known caches. These have to be depth 2 or 3 and support
MPAM's cac... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:43 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
We already have a helper for resetting an mpam class and component. Hook
it up to resctrl_arch_reset_all_ctrls() and the domain offline path.
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Ben Horgan <ben.horgan@arm.com>
---
Changes since v2:
Don't expose unlo... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:44 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
Implement resctrl_arch_get_config() by testing the live configuration for a
CPOR bitmap. For any other configuration type return the default.
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off-by: Ben Horgan <... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:45 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
resctrl has two helpers for updating the configuration.
resctrl_arch_update_one() updates a single value, and is used by the
software-controller to apply feedback to the bandwidth controls, it has to
be called on one of the CPUs in the resctrl:domain.
resctrl_arch_update_domain... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:46 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
arm64 provides helpers for changing a task's and a cpu's mpam partid/pmg
values.
These are used to back a number of resctrl_arch_ functions. Connect them
up.
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Signed-off-by: James Morse <james.morse@arm.com>
Signed-off... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:47 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
Intel RDT's CDP feature allows the cache to use a different control value
depending on whether the accesses was for instruction fetch or a data
access. MPAM's equivalent feature is the other way up: the CPU assigns a
different partid label to traffic depending on whether it was ... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:48 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: Dave Martin <Dave.Martin@arm.com>
MPAM uses a fixed-point formats for some hardware controls. Resctrl
provides the bandwidth controls as a percentage. Add helpers to convert
between these.
Ensure bwa_wd is at most 16 to make it clear higher values have no meaning.
Reviewed-by: Jonathan Cameron <jonathan.camer... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:49 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: Dave Martin <Dave.Martin@arm.com>
resctrl specifies the format of the control schemes, and these don't match
the hardware.
Some of the conversions are a bit hairy - add some kunit tests.
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Signed-off-by: Dave Martin <Dave.Martin@arm.com>
[morse: squashe... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:50 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | Because MPAM's pmg aren't identical to RDT's rmid, resctrl handles some
data structures by index. This allows x86 to map indexes to RMID, and MPAM
to map them to partid-and-pmg.
Add the helpers to do this.
Suggested-by: James Morse <james.morse@arm.com>
Signed-off-by: Ben Horgan <ben.horgan@arm.com>
---
Changes since... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:51 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | As MPAM's pmg are scoped by partid and RDT's rmid are global the
rescrl mapping to an index needs to differ.
Add some tests for the MPAM rmid mapping.
Signed-off-by: Ben Horgan <ben.horgan@arm.com>
---
drivers/resctrl/test_mpam_resctrl.c | 49 +++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
diff --gi... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:52 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | In order to calculate the rmid realloc threshold the size of the cache
needs to be known. Cache domains will also be named after the cache id. So
that this information can be extracted from cacheinfo we need to wait for
it to be ready. The cacheinfo information is populated in device_initcall()
so we wait for that.
Si... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:53 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
resctrl supports 'MB', as a percentage throttling of traffic somewhere
after the L3. This is the control that mba_sc uses, so ideally the class
chosen should be as close as possible to the counters used for mba_local.
MB's percentage control should be backed either with the fix... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:54 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
resctrl exposes a counter via a file named llc_occupancy. This isn't really
a counter as its value goes up and down, this is a snapshot of the cache
storage usage monitor.
Add some picking code to find a cache as close as possible to the L3 that
supports the CSU monitor.
If th... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:55 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
resctrl has two types of counters, NUMA-local and global. MPAM has only
bandwidth counters, but the position of the MSC may mean it counts
NUMA-local, or global traffic.
But the topology information is not available.
Apply a heuristic: the L2 or L3 supports bandwidth monitors,... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:56 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
lkml | [PATCH v3 00/47] arm_mpam: Add KVM/arm64 and resctrl glue code | This new version of the mpam missing pieces has no major rework from the
previous version. It's mainly small corrections and code tidying based on
review and things I spotted along the way. To be able to merge this we need
review from more people and people to start testing on their platforms and
giving some Tested-by ... | From: James Morse <james.morse@arm.com>
When there are enough monitors, the resctrl mbm local and total files can
be exposed. These need all the monitors that resctrl may use to be
allocated up front.
Add helpers to do this.
If a different candidate class is discovered, the old array should be
free'd and the allocat... | {
"author": "Ben Horgan <ben.horgan@arm.com>",
"date": "Mon, 12 Jan 2026 16:58:57 +0000",
"thread_id": "20260112165914.4086692-1-ben.horgan@arm.com.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.