On 9/12/25 04:43, Greg KH wrote: > On Mon, Sep 08, 2025 at 02:01:34PM -0700, Mukesh R wrote: >> On 9/6/25 04:36, Greg KH wrote: >>> On Fri, Sep 05, 2025 at 06:09:52PM -0700, Mukesh Rathor wrote: >>>> With CONFIG_HYPERV and CONFIG_HYPERV_VMBUS separated, change CONFIG_HYPERV >>>> to bool from tristate. CONFIG_HYPERV now becomes the core Hyper-V >>>> hypervisor support, such as hypercalls, clocks/timers, Confidential >>>> Computing setup, PCI passthru, etc. that doesn't involve VMBus or VMBus >>>> devices. >>> >>> But why are you making it so that this can not be a module anymore? You >>> are now forcing ALL Linux distro users to always have this code in their >>> system, despite not ever using the feature. That feels like a waste to >>> me. >>> >>> What is preventing this from staying as a module? Why must you always >>> have this code loaded at all times for everyone? >> >> This is currently not a module. I assume it was at the beginning. In >> drivers/Makefile today: >> >> obj-$(subst m,y,$(CONFIG_HYPERV)) += hv/ >> >> >> More context: CONFIG_HYPERV doesn't really reflect one module. It is >> both for kernel built in code and building of stuff in drivers/hv. >> >> drivers/hv then builds 4 modules: >> >> obj-$(CONFIG_HYPERV) += hv_vmbus.o >> obj-$(CONFIG_HYPERV_UTILS) += hv_utils.o >> obj-$(CONFIG_HYPERV_BALLOON) += hv_balloon.o >> obj-$(CONFIG_MSHV_ROOT) += mshv_root.o >> >> Notice vmbus is using CONFIG_HYPERV because there is no >> CONFIG_HYPERV_VMBUS. We are trying to fix that here. > > This series does not apply to my tree: > > checking file drivers/gpu/drm/Kconfig > checking file drivers/hid/Kconfig > checking file drivers/hv/Kconfig > Hunk #2 FAILED at 82. > 1 out of 2 hunks FAILED > checking file drivers/hv/Makefile > checking file drivers/input/serio/Kconfig > checking file drivers/net/hyperv/Kconfig > checking file drivers/pci/Kconfig > checking file drivers/scsi/Kconfig > checking file drivers/uio/Kconfig > checking file drivers/video/fbdev/Kconfig > checking file include/asm-generic/mshyperv.h > Hunk #1 succeeded at 162 with fuzz 2 (offset -3 lines). > Hunk #2 succeeded at 198 (offset -3 lines). > Hunk #3 succeeded at 215 (offset -3 lines). > checking file net/vmw_vsock/Kconfig > > What was it made against? >
Sorry to hear that. It was built against hyper-next, but perhaps I accidentally used our internal mirror. Let me rebase and send V2 right away. Thanks, -Mukesh
