messages from 2025-05-14 16:33:48 to 2025-05-29 13:38:11 UTC [more...]
[PATCH v3 00/13] PCI/TSM: Core infrastructure for PCI device security (TDISP)
2025-05-29 13:37 UTC (49+ messages)
` [PATCH v3 01/13] coco/tsm: Introduce a core device for TEE Security Managers
` [PATCH v3 02/13] PCI/IDE: Enumerate Selective Stream IDE capabilities
` [PATCH v3 03/13] PCI/TSM: Authenticate devices via platform TSM
` [PATCH v3 04/13] PCI: Enable host-bridge emulation for PCI_DOMAINS_GENERIC platforms
` [PATCH v3 05/13] PCI: vmd: Switch to pci_bus_find_emul_domain_nr()
` [PATCH v3 06/13] samples/devsec: Introduce a PCI device-security bus + endpoint sample
` [PATCH v3 07/13] PCI: Add PCIe Device 3 Extended Capability enumeration
` [PATCH v3 08/13] PCI/IDE: Add IDE establishment helpers
` [PATCH v3 09/13] PCI/IDE: Report available IDE streams
` [PATCH v3 10/13] PCI/TSM: Report active "
` [PATCH v3 11/13] samples/devsec: Add sample IDE establishment
` [PATCH v3 12/13] PCI/TSM: support TDI related operations for host TSM driver
` [RFC PATCH 1/3] coco: tsm: Add tsm_bind/unbind helpers
` [PATCH v3 13/13] PCI/TSM: Add Guest TSM Support
[PATCH v2 00/18] PCI device authentication
2025-05-29 9:40 UTC (8+ messages)
[RFC PATCH 00/30] Host side (KVM/VFIO/IOMMUFD) support for TDISP using TSM
2025-05-29 5:35 UTC (31+ messages)
` [RFC PATCH 01/30] HACK: dma-buf: Introduce dma_buf_get_pfn_unlocked() kAPI
` [RFC PATCH 02/30] vfio: Export vfio device get and put registration helpers
` [RFC PATCH 03/30] vfio/pci: Share the core device pointer while invoking feature functions
` [RFC PATCH 04/30] vfio/pci: Allow MMIO regions to be exported through dma-buf
` [RFC PATCH 05/30] fixup! vfio/pci: fix dma-buf revoke typo on reset
` [RFC PATCH 06/30] HACK: vfio/pci: Support get_pfn() callback for dma-buf
` [RFC PATCH 07/30] KVM: Support vfio_dmabuf backed MMIO region
` [RFC PATCH 08/30] KVM: x86/mmu: Handle page fault for vfio_dmabuf backed MMIO
` [RFC PATCH 09/30] KVM: x86/mmu: Handle page fault for private MMIO
` [RFC PATCH 10/30] vfio/pci: Export vfio dma-buf specific info for importers
` [RFC PATCH 11/30] KVM: vfio_dmabuf: Fetch VFIO specific dma-buf data for sanity check
` [RFC PATCH 12/30] iommufd/device: Associate a kvm pointer to iommufd_device
` [RFC PATCH 13/30] fixup! iommufd/selftest: Sync iommufd_device_bind() change to selftest
` [RFC PATCH 14/30] iommu/arm-smmu-v3-iommufd: Pass in kvm pointer to viommu_alloc
` [RFC PATCH 15/30] fixup: iommu/selftest: Sync .viommu_alloc() change to selftest
` [RFC PATCH 16/30] iommufd/viommu: track the kvm pointer & its refcount in viommu core
` [RFC PATCH 17/30] iommufd/device: Add TSM Bind/Unbind for TIO support
` [RFC PATCH 18/30] iommufd/viommu: Add trusted IOMMU configuration handlers for vdev
` [RFC PATCH 19/30] vfio/pci: Add TSM TDI bind/unbind IOCTLs for TEE-IO support
` [RFC PATCH 20/30] vfio/pci: Do TSM Unbind before zapping bars
` [RFC PATCH 21/30] iommufd/vdevice: Add TSM Guest request uAPI
` [RFC PATCH 22/30] fixup! PCI/TSM: Change the guest request type definition
` [RFC PATCH 23/30] coco/tdx_tsm: Introduce a "tdx" subsystem and "tsm" device
` [RFC PATCH 24/30] coco/tdx_tsm: TEE Security Manager driver for TDX
` [RFC PATCH 25/30] coco/tdx_tsm: Add connect()/disconnect() handlers prototype
` [RFC PATCH 26/30] coco/tdx_tsm: Add bind()/unbind()/guest_req() "
` [RFC PATCH 27/30] PCI/TSM: Add PCI driver callbacks to handle TSM requirements
` [RFC PATCH 28/30] vfio/pci: Implement TSM handlers for MMIO
` [RFC PATCH 29/30] iommufd/vdevice: Implement TSM handlers for trusted DMA
` [RFC PATCH 30/30] coco/tdx_tsm: Manage TDX Module enforced operation sequences for Unbind
[RFC PATCH v2 00/22] TSM: Secure VFIO, TDISP, SEV TIO
2025-05-29 5:30 UTC (7+ messages)
` [RFC PATCH v2 07/22] coco/tsm: Add tsm and tsm-host modules
` [RFC PATCH v2 15/22] KVM: X86: Handle private MMIO as shared
[PATCH v8 00/43] arm64: Support for Arm CCA in KVM
2025-05-29 4:52 UTC (47+ messages)
` [PATCH v8 16/43] arm64: RME: Handle realm enter/exit
` [PATCH v8 17/43] arm64: RME: Handle RMI_EXIT_RIPAS_CHANGE
` [PATCH v8 18/43] KVM: arm64: Handle realm MMIO emulation
` [PATCH v8 20/43] arm64: RME: Runtime faulting of memory
` [PATCH v8 21/43] KVM: arm64: Handle realm VCPU load
` [PATCH v8 22/43] KVM: arm64: Validate register access for a Realm VM
` [PATCH v8 29/43] arm64: RME: Always use 4k pages for realms
` [PATCH v8 30/43] arm64: RME: Prevent Device mappings for Realms
` [PATCH v8 33/43] arm64: RME: Hide KVM_CAP_READONLY_MEM for realm guests
` [PATCH v8 34/43] arm64: RME: Propagate number of breakpoints and watchpoints to userspace
` [PATCH v8 35/43] arm64: RME: Set breakpoint parameters through SET_ONE_REG
` [PATCH v8 36/43] arm64: RME: Initialize PMCR.N with number counter supported by RMM
` [PATCH v8 37/43] arm64: RME: Propagate max SVE vector length from RMM
` [PATCH v8 38/43] arm64: RME: Configure max SVE vector length for a Realm
` [PATCH v8 40/43] arm64: RME: Provide accurate register list
` [PATCH v8 43/43] KVM: arm64: Allow activating realms
[PATCH v5 0/2] kvm: sev: Add SNP guest request throttling
2025-05-28 18:25 UTC (8+ messages)
` [PATCH v5 1/2] kvm: sev: Add SEV-SNP "
` [PATCH v5 2/2] kvm: sev: If ccp is busy, report busy to guest
[PATCH 1/2] x86/sev/vc: fix efi runtime instruction emulation
2025-05-28 7:38 UTC (6+ messages)
` [PATCH 2/2] x86/sev: let sev_es_efi_map_ghcbs map the caa pages too
[PATCH v6 0/2] SEV-SNP: Add KVM support for SNP certificate fetching
2025-05-27 16:13 UTC (4+ messages)
` [PATCH v6 1/2] KVM: Introduce KVM_EXIT_SNP_REQ_CERTS for SNP certificate-fetching
SVSM Development Call May 28th, 2025
2025-05-27 15:49 UTC
[Invitation] bi-weekly guest_memfd upstream call on 2025-05-29
2025-05-27 12:32 UTC
[RFC PATCH 00/12] Private MMIO support for private assigned dev
2025-05-26 7:18 UTC (32+ messages)
[RFC, PATCH 00/12] TDX: Enable Dynamic PAMT
2025-05-23 12:00 UTC (26+ messages)
` [RFC, PATCH 05/12] KVM: TDX: Add tdx_pamt_get()/put() helpers
` [RFC, PATCH 08/12] KVM: x86/tdp_mmu: Add phys_prepare() and phys_cleanup() to kvm_x86_ops
` [RFC, PATCH 11/12] KVM: TDX: Reclaim PAMT memory
[RFC PATCH 00/20] TD-Preserving updates
2025-05-23 9:52 UTC (21+ messages)
` [RFC PATCH 01/20] x86/virt/tdx: Print SEAMCALL leaf numbers in decimal
` [RFC PATCH 02/20] x86/virt/tdx: Prepare to support P-SEAMLDR SEAMCALLs
` [RFC PATCH 03/20] x86/virt/seamldr: Introduce a wrapper for "
` [RFC PATCH 04/20] x86/virt/tdx: Introduce a "tdx" subsystem and "tsm" device
` [RFC PATCH 05/20] x86/virt/tdx: Export tdx module attributes via sysfs
` [RFC PATCH 06/20] x86/virt/seamldr: Add a helper to read P-SEAMLDR information
` [RFC PATCH 07/20] x86/virt/tdx: Expose SEAMLDR information via sysfs
` [RFC PATCH 08/20] x86/virt/seamldr: Implement FW_UPLOAD sysfs ABI for TD-Preserving Updates
` [RFC PATCH 09/20] x86/virt/seamldr: Allocate and populate a module update request
` [RFC PATCH 10/20] x86/virt/seamldr: Introduce skeleton for TD-Preserving updates
` [RFC PATCH 11/20] x86/virt/seamldr: Abort updates if errors occurred midway
` [RFC PATCH 12/20] x86/virt/seamldr: Shut down the current TDX module
` [RFC PATCH 13/20] x86/virt/tdx: Reset software states after TDX module shutdown
` [RFC PATCH 14/20] x86/virt/seamldr: Install a new TDX module
` [RFC PATCH 15/20] x86/virt/seamldr: Handle TD-Preserving update failures
` [RFC PATCH 16/20] x86/virt/seamldr: Do TDX cpu init after updates
` [RFC PATCH 17/20] x86/virt/tdx: Establish contexts for the new module
` [RFC PATCH 18/20] x86/virt/tdx: Update tdx_sysinfo and check features post-update
` [RFC PATCH 19/20] x86/virt/seamldr: Verify availability of slots for TD-Preserving updates
` [RFC PATCH 20/20] x86/virt/seamldr: Enable TD-Preserving Updates
[PATCH 3/5] KVM: gmem: Hold filemap invalidate lock while allocating/preparing folios
2025-05-21 6:46 UTC (3+ messages)
Linux kernel SIG meeting for vwfwupdate discussion
2025-05-20 14:41 UTC (7+ messages)
[PATCH v3] KVM: SEV: Disable SEV-SNP support on initialization failure
2025-05-19 19:10 UTC (3+ messages)
[PATCH v4 0/2] kvm: sev: Add SNP guest request throttling
2025-05-15 18:21 UTC (7+ messages)
` [PATCH v4 1/2] kvm: sev: Add SEV-SNP "
` [PATCH v4 2/2] kvm: sev: If ccp is busy, report busy to guest
` [PATCH v4 2/2] The ccp driver can be overloaded even with guest request rate limits. The return value of -EBUSY means that there is no firmware error to report back to user space, so the guest VM would see this as exitinfo2 = 0. The false success can trick the guest to update its message sequence number when it shouldn't have
SVSM Development Call May 14th, 2025
2025-05-15 10:08 UTC (2+ messages)
[Overview] guest_memfd extensions and dependencies 2025-05-15
2025-05-15 9:58 UTC
[PATCH v6 0/7] tsm-mr: Unified Measurement Register ABI for TVMs
2025-05-15 8:39 UTC (2+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).