Changes in Kconfig

637315cb400eed1dbe721954fea437a61a2d65b2 - Merge tag 'kvm-riscv-7.3-1' of https://github.com/kvm-riscv/linux into HEAD

Tue, 18 Aug 2026 13:07:31 +0200

Merge tag 'kvm-riscv-7.3-1' of https://github.com/kvm-riscv/linux into HEADKVM/riscv changes for 7.3- Svadu/Zicfiss/Zicfilp FWFT support for Guest- Use try_cmpxchg for IMSIC MRIF RMW- More arch-specific tracepoints in KVM RISC-V- Eager Page Splitting for KVM RISC-V- Optimize hfence request handling for SMP Guests- Improve dirty log clearing by skipping zero bits in mask- Guard HFENCE range loops against overflow- CPU PM notifiers in KVM RISC-V for non-retentive idle states- Fix kernel-mode vector context save/restore for Guest List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

efe86f088f48f18c27b648e5724048947f3b7fb4 - Merge drm/drm-next into drm-xe-next

Tue, 14 Jul 2026 15:40:31 +0200

Merge drm/drm-next into drm-xe-nextSync some i915/display changesSigned-off-by: Rodrigo Vivi List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

6d177908bad5992e17669030db41caab88041d5e - Merge drm/drm-next into drm-intel-next

Tue, 30 Jun 2026 14:55:43 +0200

Merge drm/drm-next into drm-intel-nextSync with v7.2-rc1.Signed-off-by: Jani Nikula List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

827b9aabd3ea3e96d5e48abed9f44dbd1e550d4e - Merge drm/drm-next into drm-misc-next

Tue, 30 Jun 2026 10:16:00 +0200

Merge drm/drm-next into drm-misc-nextBackmerging to get drm-misc-next to v7.2-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

7dd19adaaac9a161723a24de7c270861063ec6ac - Merge tag 'v7.2-rc1' into drm-rust-next

Sun, 28 Jun 2026 22:39:43 +0200

Merge tag 'v7.2-rc1' into drm-rust-nextMerge v7.2-rc1 into drm-rust-next to start the next cycle.Devres now requires T: 'static, which conflicts with shmem::Object usingDevres> without that bound. Resolve by adding 'staticas a supertrait to DriverObject and DeviceContext, which does notrestrict any current use cases since DriverObject is always implementedon owned, refcounted types and DeviceContext is a sealed marker traitwith only unit-type implementors.If DriverObject (or DeviceContext) ever becomes lifetime-parameterized(e.g. via a GAT for TTM backed objects), the 'static supertrait can berelaxed at that point.Signed-off-by: Danilo Krummrich List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

0eaed89c18aeedf0898baf2dbf5ff027c6795152 - Merge tag 'timers-v7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux into timers/clocksource

Mon, 17 Aug 2026 10:29:52 +0200

Merge tag 'timers-v7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux into timers/clocksource - Use designated initializers for sh_mtu2, sh_cmt, and sh_tmu, and drop the unused initializer in the platform_device_id table for sh_mtu2 (Uwe Kleine-König) - Remove redundant dev_err()/dev_err_probe() messages when devm_request_*_irq() fails, as the helper already logs an error message (Pan Chuang) - Fix a boot hang on Allwinner D1 when a forced minimum delta is used with the sun4i timer (Felix Yan) - Fix an IRQ leak in the cpuhp_setup_state() error path by freeing the IRQ on failure in the NXP PIT driver (WenTao Liang) - Fix incorrect unmapping of shared MMIO between the clocksource and clockevent drivers. If one of them fails to initialize, the error path unmaps the shared MMIO region, leaving the other driver with an invalid mapping on clps711x (Guangshuo Li) - Make the samsung_pwm driver compatible with PREEMPT_RT by replacing regular spinlocks with raw_spinlock_t in atomic contexts (Marek Szyprowski) - Use __raw_readl() and __raw_writel() instead of ioread32() and iowrite32() to support SWAP_IO_SPACE in the rtl-otto driver (Rustam Adilov) - Fix a missing clk_disable_unprepare() call in the timer initialization error path of the Armada driver (Yuho Choi)Link: https://lore.kernel.org/lkml/75feea31-683d-45a1-87f4-ab045e0152ae@oss.qualcomm.com List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

b4d85f863e5a6f1fa01b186001af0f68f4f5239e - Merge branch 'next' into for-linus

Sat, 15 Aug 2026 06:26:07 +0200

Merge branch 'next' into for-linusPrepare input updates for 7.3 merge window. List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

76904fccf81936c084faebc73ac72c0919a42941 - Merge tag 'v7.2-rc3' into next

Tue, 14 Jul 2026 04:06:00 +0200

Merge tag 'v7.2-rc3' into nextSync up with mainline to pull in stable fixes to avoid merge conflicts. List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

00599d4841790d05401820a96cf7edb193888b00 - Merge drm/drm-fixes into drm-misc-fixes

Mon, 29 Jun 2026 17:58:00 +0200

Merge drm/drm-fixes into drm-misc-fixesPull in tag v7.2-rc1 so that drm-misc-fixes becomes useful again,and drm-misc-next-fixes can be closed.Signed-off-by: Maarten Lankhorst List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

b0820861748f43759bbf4c319ed1277cff3c5921 - Merge tag 'x86_tdx_for_7.2-rc1' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip

Tue, 16 Jun 2026 02:56:12 +0200

Merge tag 'x86_tdx_for_7.2-rc1' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tipPull x86 TDX updates from Dave Hansen: "There are a few cleanups, and some changes that should allow TDX and kexec to coexist nicely. The biggest change, however, is support for updating the TDX module after boot, just like CPU microcode. TDX users really want this because it lets them do security updates without tearing things down and rebooting. - Add TDX module update support - Make kexec and TDX finally place nice together - Put TDX error codes into a single header"* tag 'x86_tdx_for_7.2-rc1' of gitolite.kernel.org:pub/scm/linux/kernel/git/tip/tip: (30 commits) x86/virt/tdx: Document TDX module update x86/virt/tdx: Enable TDX module runtime updates x86/virt/tdx: Refresh TDX module version after update coco/tdx-host: Lock out module updates when reading version x86/virt/seamldr: Add module update locking x86/virt/tdx: Restore TDX module state x86/virt/seamldr: Initialize the newly-installed TDX module x86/virt/seamldr: Install a new TDX module x86/virt/tdx: Reset software states during TDX module shutdown x86/virt/seamldr: Shut down the current TDX module x86/virt/seamldr: Abort updates after a failed step x86/virt/seamldr: Introduce skeleton for TDX module updates x86/virt/seamldr: Allocate and populate a module update request coco/tdx-host: Implement firmware upload sysfs ABI for TDX module updates coco/tdx-host: Don't expose P-SEAMLDR information on CPUs with erratum coco/tdx-host: Expose P-SEAMLDR information via sysfs x86/virt/seamldr: Add a helper to retrieve P-SEAMLDR information x86/virt/seamldr: Introduce a wrapper for P-SEAMLDR SEAMCALLs coco/tdx-host: Expose TDX module version coco/tdx-host: Introduce a "tdx_host" device ... List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

c3e70c5ee53f1a5e1df2e83f846185154d58111f - coco/tdx-host: Implement firmware upload sysfs ABI for TDX module updates

Thu, 21 May 2026 00:29:00 +0200

coco/tdx-host: Implement firmware upload sysfs ABI for TDX module updatestl;dr: Select fw_upload for doing TDX module updates. The process ofselecting among available update images is complicated and nuanced. Puntthe selection process out to userspace. One existing userspaceimplementation today is the script in the Intel TDX Module Binariesrepository[1].Long Version:The kernel supports two primary firmware update mechanisms: 1. request_firmware() - used by microcode, SEV firmware, hundreds of other drivers 2. 'struct fw_upload' - used by CXL, FPGA updates, dozens of othersThe key difference between is that request_firmware() loads a named filefrom the filesystem where the filename is kernel-controlled, whilefw_upload accepts firmware data directly from userspace.TDX module firmware update selection policy is too complex for the kernel.Leave it to userspace and use fw_upload.Add a skeleton fw_upload implementation to be fleshed out in subsequentpatches.Refactor the sysfs visiblity attribute function so it can be used as amore generic flag for the presence of viable runtime update support.Why fw_upload instead of request_firmware()?============================================Selecting a TDX module update image is not a simple "load the latest"decision. Userspace needs to choose an image that is compatible with boththe platform and the currently running module.Some constraints are hard requirements:a. Module version series are platform-specific. For example, the 1.5.x series runs on Sapphire Rapids but not Granite Rapids, which needs 2.0.x.b. Updates are also constrained by version distance. A 1.5.6 module might permit updates to 1.5.7 but not to 1.5.50.There may also be userspace policy choices:c. Decide the update direction: upgrade or downgraded. Choose whether to optimize for fewer updates or smaller version steps, for example, 1.2.3=>1.2.5 versus 1.2.3=>1.2.4=>1.2.5.Given that complexity, leave module selection to userspace and usefw_upload.1. https://github.com/intel/confidential-computing.tdx.tdx-module.binaries/blob/main/version_select_and_load.py[ dhansen: add version script link, add more explanation of code moves, fix some minor whitespace issues ]Signed-off-by: Chao Gao Signed-off-by: Dave Hansen Reviewed-by: Tony Lindgren Reviewed-by: Kai Huang Reviewed-by: Kiryl Shutsemau (Meta) Link: https://lore.kernel.org/kvm/01fc8946-eb84-46fa-9458-f345dd3f6033@intel.com/Link: https://patch.msgid.link/20260520133909.409394-13-chao.gao@intel.com List of files: /linux/drivers/virt/coco/tdx-host/Kconfig

59783353467958517a3e511394d7ab3aed03bc6a - coco/tdx-host: Introduce a "tdx_host" device

Thu, 21 May 2026 00:28:52 +0200

coco/tdx-host: Introduce a "tdx_host" deviceTDX depends on a platform firmware module that runs on the CPU.Unlike other CoCo architectures, TDX has no hardware "device"running the show, just a blob on the CPU.Create a virtual device to anchor interactions with this platformfirmware. This lets later code: - expose metadata: TDX module version, seamldr version, to userspace as device attributes - implement firmware uploader APIs (which are tied to a device) to support TDX module runtime updatesUse a faux device because the TDX module is singular within the systemand has no platform resources. Using a faux device eliminates the needto create a stub bus.The call to tdx_get_sysinfo() ensures that the TDX module is ready toprovide services.Note that AMD has a PCI device for the PSP for SEV and ARM CCA willlikely have a faux device [1].Thanks to Dan and Yilun for all the help on this one.[ dhansen: trim changelog ]Signed-off-by: Chao Gao Signed-off-by: Dave Hansen Reviewed-by: Jonathan Cameron Reviewed-by: Tony Lindgren Reviewed-by: Xu Yilun Reviewed-by: Kai Huang Reviewed-by: Kiryl Shutsemau (Meta) Reviewed-by: Xiaoyao Li Link: https://lore.kernel.org/all/2025073035-bulginess-rematch-b92e@gregkh/ # [1]Link: https://patch.msgid.link/20260520133909.409394-7-chao.gao@intel.com List of files: /linux/drivers/virt/coco/tdx-host/Kconfig