linux-kernel - Re: Subject: [PATCH v2] vmbus: retrieve connection-id from DeviceTree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250604032721.GA31886@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
Date: Tue, 3 Jun 2025 20:27:21 -0700
From: Saurabh Singh Sengar <ssengar@...ux.microsoft.com>
To: Hardik Garg <hargar@...ux.microsoft.com>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, wei.liu@...nel.org,
	decui@...rosoft.com, ssengar@...rosoft.com,
	romank@...ux.microsoft.com, linux-hyperv@...r.kernel.org,
	linux-kernel@...r.kernel.org, stable@...nel.org,
	apais@...rosoft.com
Subject: Re: Subject: [PATCH v2] vmbus: retrieve connection-id from DeviceTree

On Tue, Jun 03, 2025 at 02:01:00PM -0700, Hardik Garg wrote:
> The connection-id determines which hypervisor communication channel the
> guest should use to talk to the VMBus host. This patch adds support to
> read this value from the DeviceTree where it exists as a property under
> the vmbus node with the compatible ID "microsoft,message-connection-id".
> The property name follows the format <vendor>,<field> where
> "vendor": "microsoft" and "field": "message-connection-id"
> 
> Reading from DeviceTree allows platforms to specify their preferred
> communication channel, making it more flexible. If the property is
> not found in the DeviceTree, use the default connection ID
> (VMBUS_MESSAGE_CONNECTION_ID or VMBUS_MESSAGE_CONNECTION_ID_4
> based on protocol version).
> 
> Signed-off-by: Hardik Garg <hargar@...ux.microsoft.com>
> ---
> v2:
> - Rebased on hyperv-next branch as requested by maintainers
> - Added details about the property name format in the commit message

Property need to be documented in Documentation/devicetree/bindings/bus/microsoft,vmbus.yaml

- Saurabh

>