From: Hardik Garg <hargar@linux.microsoft.com>
To: krzk@kernel.org
Cc: apais@microsoft.com, cho@microsoft.com, conor+dt@kernel.org,
decui@microsoft.com, devicetree@vger.kernel.org,
haiyangz@microsoft.com, hargar@linux.microsoft.com,
hargar@microsoft.com, krzk+dt@kernel.org, kys@microsoft.com,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org, ssengar@linux.microsoft.com, wei.liu@kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: microsoft: Add vmbus message-connection-id property
Date: Thu, 24 Jul 2025 15:12:13 -0700 [thread overview]
Message-ID: <1753395133-26061-1-git-send-email-hargar@linux.microsoft.com> (raw)
In-Reply-To: <6d3b5d1e-de1b-4d3b-ba14-7029c51b8e05@kernel.org>
> Then all guests can use the same value, 0, making this property redundant.
No, they cannot use the same value. The protocol requires different connection IDs for different communication paths.
For example, a guest communicating with a VTL0 control plane uses a different connection ID than one communicating with
a VTL2 control plane. The host specifies this value based on the guest's configuration, and there is no other discovery
method available to determine the correct connection ID.
> So not suitable for DT. DT is a static data. You cannot just keep changing existing DT to match whatever you want runtime.
From the guest's perspective, this data is completely static - it doesn't change over the lifetime of the guest.
The guest always looks it up in DT. The hypervisor merely populates this value in the guest's DT. Once set, it remains
fixed for that guest instance, so this data is not dynamic, it's completely fixed for the guest.
Thanks,
Hardik
next prev parent reply other threads:[~2025-07-24 22:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 23:06 [PATCH v4 0/2] vmbus: Add DeviceTree support for message connection-id Hardik Garg
2025-06-19 23:06 ` [PATCH v4 1/2] dt-bindings: microsoft: Add vmbus message-connection-id property Hardik Garg
2025-06-20 7:21 ` Krzysztof Kozlowski
2025-07-14 7:48 ` Hardik Garg
2025-07-14 7:56 ` Krzysztof Kozlowski
2025-07-16 4:42 ` Hardik Garg
2025-07-16 14:35 ` Krzysztof Kozlowski
2025-07-23 3:08 ` Hardik Garg
2025-07-23 6:18 ` Krzysztof Kozlowski
2025-07-24 22:12 ` Hardik Garg [this message]
2025-07-25 7:32 ` Krzysztof Kozlowski
2025-06-19 23:06 ` [PATCH v4 2/2] vmbus: retrieve connection-id from DeviceTree Hardik Garg
2025-06-20 2:36 ` Michael Kelley
2025-06-20 7:22 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1753395133-26061-1-git-send-email-hargar@linux.microsoft.com \
--to=hargar@linux.microsoft.com \
--cc=apais@microsoft.com \
--cc=cho@microsoft.com \
--cc=conor+dt@kernel.org \
--cc=decui@microsoft.com \
--cc=devicetree@vger.kernel.org \
--cc=haiyangz@microsoft.com \
--cc=hargar@microsoft.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ssengar@linux.microsoft.com \
--cc=wei.liu@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).