[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SA1PR21MB13354BFC68B9791FCE469763BF4E9@SA1PR21MB1335.namprd21.prod.outlook.com>
Date: Thu, 22 Sep 2022 20:07:19 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Wei Liu <wei.liu@...nel.org>,
Stanislav Kinsburskii <skinsburskii@...ux.microsoft.com>
CC: Stanislav Kinsburskii <skinsburskii@...rosoft.com>,
Stanislav Kinsburskiy <stanislav.kinsburskiy@...il.com>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Michael Kelley (LINUX)" <mikelley@...rosoft.com>
Subject: RE: [PATCH] Drivers: hv: vmbus: Don't wait for the ACPI device upon
initialization
> From: Wei Liu <wei.liu@...nel.org>
> Sent: Thursday, September 22, 2022 10:20 AM
> ...
> On Wed, Sep 21, 2022 at 06:39:05PM +0000, Stanislav Kinsburskii wrote:
> > From: Stanislav Kinsburskiy <stanislav.kinsburskiy@...il.com>
> >
> > Waiting to 5 seconds in case of missing VMBUS ACPI device is redundant as
> the
> > device is either present already or won't be available at all.
> > This patch enforces synchronous probing to make sure the bus traversal,
> > happening upon driver registering will either find the device (if present) or
> > not spend any additional time if device is absent.
> >
> > Signed-off-by: Stanislav Kinsburskiy <stanislav.kinsburskiy@...il.com>
> > CC: "K. Y. Srinivasan" <kys@...rosoft.com>
> > CC: Haiyang Zhang <haiyangz@...rosoft.com>
> > CC: Stephen Hemminger <sthemmin@...rosoft.com>
> > CC: Wei Liu <wei.liu@...nel.org>
> > CC: Dexuan Cui <decui@...rosoft.com>
> > CC: linux-hyperv@...r.kernel.org
> > CC: linux-kernel@...r.kernel.org
>
> Looks good to me. I will wait for a few days for others to chime in.
>
> CC Michael.
Looks good to me.
Reviewed-by: Dexuan Cui <decui@...rosoft.com>
Powered by blists - more mailing lists