[bug report] Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl

Hello Rick Edgecombe, Commit 211f514ebf1e ("Drivers: hv: vmbus: Track decrypted status in vmbus_gpadl") from Mar 11, 2024 (linux-next), leads to the following Smatch static checker warning: drivers/hv/channel.c:870 vmbus_teardown_gpadl() warn: assigning signed to unsigned: 'gpadl-

Re: [RFC PATCH net-next v6 07/14] virtio/vsock: add common datagram send path

On Tue, Jul 23, 2024 at 7:42 AM Stefano Garzarella wrote: > > On Wed, Jul 10, 2024 at 09:25:48PM GMT, Amery Hung wrote: > >From: Bobby Eshleman > > > >This commit implements the common function > >virtio_transport_dgram_enqueue for enqueueing datagrams. It does not add > >usage in either vhost or

[PATCH v3 7/7] PCI: hv: Get vPCI MSI IRQ domain from DT

The hyperv-pci driver uses ACPI for MSI IRQ domain configuration on arm64. It won't be able to do that in the VTL mode where only DeviceTree can be used. Update the hyperv-pci driver to get vPCI MSI IRQ domain in the DeviceTree case, too. Signed-off-by: Roman Kisel --- drivers/hv/vmbus_drv.c

[PATCH v3 6/7] Drivers: hv: vmbus: Get the IRQ number from DT

The VMBus driver uses ACPI for interrupt assignment on arm64 hence it won't function in the VTL mode where only DeviceTree can be used. Update the VMBus driver to discover interrupt configuration via DeviceTree and indicate DMA cache coherency. Signed-off-by: Roman Kisel --- drivers/hv/vmbus_dr

[PATCH v3 5/7] dt-bindings: bus: Add Hyper-V VMBus cache coherency and IRQs

Add dt-bindings for the Hyper-V VMBus DMA cache coherency and interrupt specification. Signed-off-by: Roman Kisel --- .../devicetree/bindings/bus/microsoft,vmbus.yaml | 11 +++ 1 file changed, 11 insertions(+) diff --git a/Documentation/devicetree/bindings/bus/microsoft,vmbus.yaml

[PATCH v3 3/7] Drivers: hv: Provide arch-neutral implementation of get_vtl()

To run in the VTL mode, Hyper-V drivers have to know what VTL the system boots in, and the arm64/hyperv code does not have the means to compute that. Refactor the code to hoist the function that detects VTL, make it arch-neutral to be able to employ it to get the VTL on arm64. Fix the hypercall ou

[PATCH v3 4/7] arm64: hyperv: Boot in a Virtual Trust Level

To run in the VTL mode, Hyper-V drivers have to know what VTL the system boots in, and the arm64/hyperv code does not update the variable that stores the value. Update the variable to enable the Hyper-V drivers to boot in the VTL mode and print the VTL the code runs in. Signed-off-by: Roman Kisel

[PATCH v3 2/7] Drivers: hv: Enable VTL mode for arm64

Kconfig dependencies for arm64 guests on Hyper-V require that be ACPI enabled, and limit VTL mode to x86/x64. To enable VTL mode on arm64 as well, update the dependencies. Since VTL mode requires DeviceTree instead of ACPI, don’t require arm64 guests on Hyper-V to have ACPI. Signed-off-by: Roman K

[PATCH v3 1/7] arm64: hyperv: Use SMC to detect hypervisor presence

The arm64 Hyper-V startup path relies on ACPI to detect running under a Hyper-V compatible hypervisor. That doesn't work on non-ACPI systems. Hoist the ACPI detection logic into a separate function, use the new SMC added recently to Hyper-V to use in the non-ACPI case. Signed-off-by: Roman Kisel

[PATCH v3 0/7] arm64: hyperv: Support Virtual Trust Level Boot

This patch set enables the Hyper-V code to boot on ARM64 inside a Virtual Trust Level. These levels are a part of the Virtual Secure Mode documented in the Top-Level Functional Specification available at https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/tlfs/vsm [V3] - Employ

Re: [PATCH] Drivers: hv: vmbus: Deferring per cpu tasks

On Fri, Jul 26, 2024 at 06:34:53AM +, Srivatsa S. Bhat wrote: > On Fri, Jul 26, 2024 at 12:01:33AM +, Dexuan Cui wrote: > > > From: Saurabh Singh Sengar > > > Sent: Thursday, July 25, 2024 8:35 AM > > > Subject: Re: [PATCH] Drivers: hv: vmbus: Deferring per cpu tasks > > > > Without the p