From: Roman Kisel <romank@linux.microsoft.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: Saurabh Singh Sengar <ssengar@microsoft.com>,
Naman Jain <namjain@linux.microsoft.com>,
KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Dexuan Cui <decui@microsoft.com>,
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 11:13:33 -0700 [thread overview]
Message-ID: <2cd63d5d-21af-408b-869a-b38118f4cad6@linux.microsoft.com> (raw)
In-Reply-To: <aBztdK82ZQQvnWsh@liuwe-devbox-ubuntu-v2.tail21d00.ts.net>
On 5/8/2025 10:44 AM, Wei Liu wrote:
> On Thu, May 08, 2025 at 08:44:14AM -0700, Roman Kisel wrote:
[...]
>>
>> 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.
>>
>
> I don't think this is an absurd request.
>
> While obviously Microsoft will only build the code as builtin, there are
> bots that do randconfig build tests but never run the resulting binary.
Thanks, Wei, for the thorough explanation!
>
> Thanks,
> Wei.
>
>>>
>>> - 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
>>
--
Thank you,
Roman
next prev parent reply other threads:[~2025-05-08 18:13 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
2025-05-08 17:44 ` Wei Liu
2025-05-08 18:13 ` Roman Kisel [this message]
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=2cd63d5d-21af-408b-869a-b38118f4cad6@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®