[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZnkcBivQwrCEmcK_@liuwe-devbox-debian-v2>
Date: Mon, 24 Jun 2024 07:11:02 +0000
From: Wei Liu <wei.liu@...nel.org>
To: mhklinux@...look.com
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, wei.liu@...nel.org,
decui@...rosoft.com, tglx@...utronix.de, mingo@...hat.com,
bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, lpieralisi@...nel.org, kw@...ux.com, robh@...nel.org,
bhelgaas@...gle.com, James.Bottomley@...senpartnership.com,
martin.petersen@...cle.com, arnd@...db.de,
linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org, linux-scsi@...r.kernel.org,
linux-arch@...r.kernel.org, maz@...nel.org, den@...inux.co.jp,
jgowans@...zon.com, dawei.li@...ngroup.cn
Subject: Re: [RFC 01/12] Drivers: hv: vmbus: Drop unsupported VMBus devices
earlier
On Mon, Jun 03, 2024 at 10:09:29PM -0700, mhkelley58@...il.com wrote:
> From: Michael Kelley <mhklinux@...look.com>
>
> Because Hyper-V doesn't know ahead-of-time what operating system will be
> running in a guest VM, it may offer to Linux guests VMBus devices that are
> intended for use only in Windows guests. Currently in Linux, VMBus
> channels are created for these devices, and they are processed by
> vmbus_device_register(). While nothing further happens because no matching
> driver is found, the channel continues to exist.
>
> To avoid having the spurious channel, drop such devices immediately in
> vmbus_onoffer(), based on identifying the device in the
> vmbus_unsupported_devs table. If Hyper-V should issue a rescind request
> for the device, no matching channel will be found and the rescind will
> also be ignored.
>
> Since unsupported devices are dropped early, the check for unsupported
> devices in hv_get_dev_type() is redundant. Remove it.
>
> Signed-off-by: Michael Kelley <mhklinux@...look.com>
Acked-by: Wei Liu <wei.liu@...nel.org>
Powered by blists - more mailing lists