From: Naman Jain <namjain@linux.microsoft.com>
To: Saurabh Singh Sengar <ssengar@linux.microsoft.com>
Cc: "K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
John Starks <jostarks@microsoft.com>,
jacob.pan@linux.microsoft.com,
Easwar Hariharan <eahariha@linux.microsoft.com>
Subject: Re: [PATCH 1/2] Drivers: hv: vmbus: Wait for offers during boot
Date: Tue, 22 Oct 2024 15:25:00 +0530 [thread overview]
Message-ID: <91756da8-f2c3-482a-95ee-6208e1205502@linux.microsoft.com> (raw)
In-Reply-To: <20241021045724.GB25279@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On 10/21/2024 10:27 AM, Saurabh Singh Sengar wrote:
> On Fri, Oct 18, 2024 at 04:58:10AM -0700, Naman Jain wrote:
>> Channels offers are requested during vmbus initialization and resume
>
> Nit: s/vmbus/VMBus
Thanks for reviewing Saurabh.
Noted this for next patch. Thanks
>
>> from hibernation. Add support to wait for all channel offers to be
>> delivered and processed before returning from vmbus_request_offers.
>> This is to support user mode (VTL0) in OpenHCL (A Linux based
>> paravisor for Confidential VMs) to ensure that all channel offers
>> are present when init begins in VTL0, and it knows which channels
>> the host has offered and which it has not.
>
> Usermode isn't necessarily of VTL0, and this issue was actually identified
> at a higher VTL in OpenHCL. However, this change isn't specific to OpenHCL,
> but is intended for general use. I would prefer if the commit message were
> either more generic or precisely aligned with the specific issue it's
> addressing.
>
I'll make it generic.
>>
>> This is in analogy to a PCI bus not returning from probe until it has
>> scanned all devices on the bus.
>>
>> Without this, user mode can race with vmbus initialization and miss
>> channel offers. User mode has no way to work around this other than
>> sleeping for a while, since there is no way to know when vmbus has
>> finished processing offers.
>>
>> With this added functionality, remove earlier logic which keeps track
>> of count of offered channels post resume from hibernation. Once all
>> offers delivered message is received, no further offers are going to
>> be received. Consequently, logic to prevent suspend from happening
>> after previous resume had missing offers, is also removed.
>>
>> Co-developed-by: John Starks <jostarks@microsoft.com>
>> Signed-off-by: John Starks <jostarks@microsoft.com>
>> Signed-off-by: Naman Jain <namjain@linux.microsoft.com>
>> ---
>> drivers/hv/channel_mgmt.c | 38 +++++++++++++++++++++++---------------
>> drivers/hv/connection.c | 4 ++--
>> drivers/hv/hyperv_vmbus.h | 14 +++-----------
<..>
>> }
>>
>> + /* Wait for the host to send all offers. */
>> + while (wait_for_completion_timeout(
>> + &vmbus_connection.all_offers_delivered_event, msecs_to_jiffies(10 * 1000)) == 0) {
>
> Nit: Can simply put 10000 instead of 10*1000
Noted.
>
>> + pr_warn("timed out waiting for all offers to be delivered...\n");
>
> I know we are moving from async to sync, so earlier we never checked this.
> But what if some channel timed out do we want to handle this case ? Or put
> a comment why this is OK.
>
> We could set error from here as well, but I see vmbus_request_offers return value
> is never checked.
It seems to be a best effort way to get all the offers. If its not
received in time, I think we can print a warning and continue. I can add
that to a comment.
>
>> + }
>> +
>> + /*
>> + * Flush handling of offer messages (which may initiate work on
>> + * other work queues).
>> + */
Regards,
Naman
next prev parent reply other threads:[~2024-10-22 9:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 11:58 [PATCH 0/2] Drivers: hv: vmbus: Wait for offers and log missing offers Naman Jain
2024-10-18 11:58 ` [PATCH 1/2] Drivers: hv: vmbus: Wait for offers during boot Naman Jain
2024-10-18 22:52 ` Easwar Hariharan
2024-10-21 4:33 ` Michael Kelley
2024-10-22 9:50 ` Naman Jain
2024-10-22 18:03 ` Michael Kelley
2024-10-25 18:18 ` Dexuan Cui
2024-10-28 15:21 ` Michael Kelley
2024-10-28 4:54 ` Naman Jain
2024-10-21 4:57 ` Saurabh Singh Sengar
2024-10-22 9:55 ` Naman Jain [this message]
2024-10-22 17:38 ` Michael Kelley
2024-10-24 10:32 ` Naman Jain
2024-10-18 11:58 ` [PATCH 2/2] Drivers: hv: vmbus: Log on missing offers Naman Jain
2024-10-21 2:43 ` Easwar Hariharan
2024-10-21 4:26 ` Saurabh Singh Sengar
2024-10-21 4:31 ` Naman Jain
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=91756da8-f2c3-482a-95ee-6208e1205502@linux.microsoft.com \
--to=namjain@linux.microsoft.com \
--cc=decui@microsoft.com \
--cc=eahariha@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jacob.pan@linux.microsoft.com \
--cc=jostarks@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.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