From: Roman Kisel <romank@linux.microsoft.com>
To: Saurabh Singh Sengar <ssengar@microsoft.com>,
Naman Jain <namjain@linux.microsoft.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>
Cc: Anirudh Rayabharam <anrayabh@linux.microsoft.com>,
Saurabh Sengar <ssengar@linux.microsoft.com>,
Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>,
Nuno Das Neves <nunodasneves@linux.microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: Re: [PATCH] Drivers: hv: Introduce mshv_vtl driver
Date: Thu, 8 May 2025 08:44:14 -0700 [thread overview]
Message-ID: <1edea7f4-5ad2-4103-8eb5-9d5d9f0c7b0d@linux.microsoft.com> (raw)
In-Reply-To: <KUZP153MB14448028621F8148D5129D9FBE8BA@KUZP153MB1444.APCP153.PROD.OUTLOOK.COM>
On 5/7/2025 8:00 PM, Saurabh Singh Sengar wrote:
>>
>> On 5/7/2025 4:21 AM, Naman Jain wrote:
>>>
>>>
>>
>> [...]
>>
>>> <snip>
>>>
>>>>> + return -EINVAL;
>>>>> + if (copy_from_user(payload, (void __user *)message.payload_ptr,
>>>>> + message.payload_size))
>>>>> + return -EFAULT;
>>>>> +
>>>>> + return hv_post_message((union
>>>>
>>>> This function definition is in separate file which can be build as
>>>> independent module, this will cause problem while linking . Try
>>>> building with CONFIG_HYPERV=m and check.
>>>>
>>>> - Saurabh
>>>
>>> Thanks for reviewing Saurabh. As CONFIG_HYPERV can be set to 'm'
>>> and CONFIG_MSHV_VTL depends on it, changing CONFIG_MSHV_VTL to
>>> tristate and a few tweaks in Makefile will fix this issue. This will
>>> ensure that mshv_vtl is also built as a module when hyperv is built as a
>> module.
>>>
>>> I'll take care of this in next version.
>>
>> Let me ask for a clarification. How would the system boot if CONFIG_HYPERV
>> is set to m? The arch parts are going to be still compiled-in, correct?
>> Otherwise I don't see how that would initialize.
>>
>> I am thinking who would load Hyper-V modules on the system that requires
>> Hyper-V here. It is understandable that distro's build Hyper-V as a module.
>> That way, they don't have to load anything when there is no Hyper-V. Here, it
>> is Hyper-V in and out, what do we need to fix?
>
> We need to fix compilation - for everyone.
You seem to know for whom it is broken, would be great to share this
knowledge. When CONFIG_MSHV_VTL is set to "m", OpenHCL will break down
without additional work. So why do we need to be able to build that
as a module, to let someone build the firmware that doesn't work?
So far the request comes off as absurd to me.
>
> - Saurabh
>
>>
>>>
>>> here is the diff for reference:
>>> diff --git a/drivers/hv/Kconfig b/drivers/hv/Kconfig index
>>> 57dcfcb69b88..c7f21b483377 100644
>>> --- a/drivers/hv/Kconfig
>>> +++ b/drivers/hv/Kconfig
>>> @@ -73,7 +73,7 @@ config MSHV_ROOT
>>> If unsure, say N.
>>>
>>> config MSHV_VTL
>>> - bool "Microsoft Hyper-V VTL driver"
>>> + tristate "Microsoft Hyper-V VTL driver"
>>> depends on HYPERV && X86_64
>>> depends on TRANSPARENT_HUGEPAGE
>>> depends on OF
>>> diff --git a/drivers/hv/Makefile b/drivers/hv/Makefile index
>>> 5e785dae08cc..c53a0df746b7 100644
>>> --- a/drivers/hv/Makefile
>>> +++ b/drivers/hv/Makefile
>>> @@ -15,9 +15,11 @@ hv_vmbus-$(CONFIG_HYPERV_TESTING) +=
>>> hv_debugfs.o
>>> hv_utils-y := hv_util.o hv_kvp.o hv_snapshot.o hv_utils_transport.o
>>> mshv_root-y := mshv_root_main.o mshv_synic.o mshv_eventfd.o
>>> mshv_irq.o \
>>> mshv_root_hv_call.o mshv_portid_table.o
>>> +mshv_vtl-y := mshv_vtl_main.o
>>>
>>> # Code that must be built-in
>>> obj-$(subst m,y,$(CONFIG_HYPERV)) += hv_common.o -obj-$(subst
>>> m,y,$(CONFIG_MSHV_ROOT)) += hv_proc.o mshv_common.o
>>> -
>>> -mshv_vtl-y := mshv_vtl_main.o mshv_common.o
>>> +obj-$(subst m,y,$(CONFIG_MSHV_ROOT)) += hv_proc.o ifneq
>>> +($(CONFIG_MSHV_ROOT) $(CONFIG_MSHV_VTL),)
>>> + obj-y += mshv_common.o
>>> +endif
>>>
>>> Regards,
>>> Naman
>>
>> --
>> Thank you,
>> Roman
>
--
Thank you,
Roman
next prev parent reply other threads:[~2025-05-08 15:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 8:49 Naman Jain
2025-05-06 15:48 ` Roman Kisel
2025-05-07 10:19 ` Saurabh Singh Sengar
2025-05-07 11:21 ` Naman Jain
2025-05-07 20:31 ` Roman Kisel
2025-05-08 3:00 ` Saurabh Singh Sengar
2025-05-08 15:44 ` Roman Kisel [this message]
2025-05-08 17:44 ` Wei Liu
2025-05-08 18:13 ` Roman Kisel
2025-05-07 13:02 ` Saurabh Singh Sengar
2025-05-07 19:20 ` Roman Kisel
2025-05-08 2:59 ` Saurabh Singh Sengar
2025-05-09 18:07 ` Roman Kisel
2025-05-08 4:03 ` Michael Kelley
2025-05-08 15:34 ` Roman Kisel
2025-05-08 18:03 ` Wei Liu
2025-05-09 18:02 ` [EXTERNAL] " Saurabh Singh Sengar
2025-05-09 18:05 ` Roman Kisel
2025-05-12 4:57 ` Naman Jain
2025-05-13 15:30 ` Michael Kelley
2025-05-13 16:34 ` Naman Jain
2025-05-12 4:55 ` Naman Jain
2025-05-10 20:55 ` [External] : " ALOK TIWARI
2025-05-12 14:04 ` 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=1edea7f4-5ad2-4103-8eb5-9d5d9f0c7b0d@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=anrayabh@linux.microsoft.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjain@linux.microsoft.com \
--cc=nunodasneves@linux.microsoft.com \
--cc=skinsburskii@linux.microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@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
all inboxes | Powered by JetHome®