From: Mukesh R <mrathor@linux.microsoft.com>
To: Michael Kelley <mhklinux@outlook.com>, Wei Liu <wei.liu@kernel.org>
Cc: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"kys@microsoft.com" <kys@microsoft.com>,
"haiyangz@microsoft.com" <haiyangz@microsoft.com>,
"decui@microsoft.com" <decui@microsoft.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>, "arnd@arndb.de" <arnd@arndb.de>
Subject: Re: [PATCH v3 0/6] Hyper-V: Implement hypervisor core collection
Date: Mon, 20 Oct 2025 12:05:19 -0700 [thread overview]
Message-ID: <4a4fa302-18fa-ba01-ec06-d4bf0cc84032@linux.microsoft.com> (raw)
In-Reply-To: <SN6PR02MB4157C70EBD25315F098DB3A1D4F7A@SN6PR02MB4157.namprd02.prod.outlook.com>
On 10/17/25 19:54, Michael Kelley wrote:
> From: Mukesh R <mrathor@linux.microsoft.com> Sent: Friday, October 17, 2025 4:58 PM
>>
>> On 10/17/25 15:57, Wei Liu wrote:
>>> On Fri, Oct 17, 2025 at 10:33:00PM +0000, Wei Liu wrote:
>>>> On Mon, Oct 06, 2025 at 03:42:02PM -0700, Mukesh Rathor wrote:
>>>> [...]
>>>>> Mukesh Rathor (6):
>>>>> x86/hyperv: Rename guest crash shutdown function
>>>>> hyperv: Add two new hypercall numbers to guest ABI public header
>>>>> hyperv: Add definitions for hypervisor crash dump support
>>>>> x86/hyperv: Add trampoline asm code to transition from hypervisor
>>>>> x86/hyperv: Implement hypervisor RAM collection into vmcore
>>>>> x86/hyperv: Enable build of hypervisor crashdump collection files
>>>>>
>>>>
>>>> Applied to hyperv-next. Thanks.
>>>
>>> This breaks i386 build.
>>>
>>> /work/linux-on-hyperv/linux.git/arch/x86/hyperv/hv_init.c: In function ?hyperv_init?:
>>> /work/linux-on-hyperv/linux.git/arch/x86/hyperv/hv_init.c:557:17: error: implicit declaration of function ?hv_root_crash_init? [-Werror=implicit-function-declaration]
>>> 557 | hv_root_crash_init();
>>> | ^~~~~~~~~~~~~~~~~~
>>>
>>> That's because CONFIG_MSHV_ROOT is only available on x86_64. And the
>>> crash feature is guarded by CONFIG_MSHV_ROOT.
>>>
>>> Applying the following diff fixes the build.
>>
>>
>> Thanks. A bit surprising tho that CONFIG_MSHV_ROOT doesn't have
>> hard dependency on x86_64. It should, no?
>
> CONFIG_MSHV_ROOT *does* have a hard dependency on X86_64.
>
> But the problem is actually more pervasive than just 32-bit builds. Because
> of the hard dependency, 32-bit builds imply CONFIG_MSHV_ROOT=n, which is
> the real problem. In arch/x86/include/asm/mshyperv.h the declaration for
> hv_root_crash_init() is available only when CONFIG_MSHV_ROOT is defined
> (m or y). There's a stub hv_root_crash_init() if CONFIG_MSHV_ROOT is defined
> and CONFIG_CRASH_DUMP=n, but not if CONFIG_MSHV_ROOT=n. The solution
> is to add a stub when CONFIG_MSHV_ROOT=n, as below:
>
> diff --git a/arch/x86/include/asm/mshyperv.h b/arch/x86/include/asm/mshyperv.h
> index 76582affefa8..a5b258d268ed 100644
> --- a/arch/x86/include/asm/mshyperv.h
> +++ b/arch/x86/include/asm/mshyperv.h
> @@ -248,6 +248,8 @@ void hv_crash_asm_end(void);
> static inline void hv_root_crash_init(void) {}
> #endif /* CONFIG_CRASH_DUMP */
>
> +#else /* CONFIG_MSHV_ROOT */
> +static inline void hv_root_crash_init(void) {}
> #endif /* CONFIG_MSHV_ROOT */
>
> #else /* CONFIG_HYPERV */
>
> Annoyingly, this solution duplicates the hv_root_crash_init() stub. So
> an alternate approach that changes a few more lines of code is this:
>
> diff --git a/arch/x86/include/asm/mshyperv.h b/arch/x86/include/asm/mshyperv.h
> index 76582affefa8..1342d55c2545 100644
> --- a/arch/x86/include/asm/mshyperv.h
> +++ b/arch/x86/include/asm/mshyperv.h
> @@ -237,18 +237,14 @@ static __always_inline u64 hv_raw_get_msr(unsigned int reg)
> }
> int hv_apicid_to_vp_index(u32 apic_id);
>
> -#if IS_ENABLED(CONFIG_MSHV_ROOT)
> -
> -#ifdef CONFIG_CRASH_DUMP
> +#if IS_ENABLED(CONFIG_MSHV_ROOT) && IS_ENABLED(CONFIG_CRASH_DUMP)
> void hv_root_crash_init(void);
> void hv_crash_asm32(void);
> void hv_crash_asm64(void);
> void hv_crash_asm_end(void);
> -#else /* CONFIG_CRASH_DUMP */
> +#else /* CONFIG_MSHV_ROOT && CONFIG_CRASH_DUMP */
> static inline void hv_root_crash_init(void) {}
> -#endif /* CONFIG_CRASH_DUMP */
> -
> -#endif /* CONFIG_MSHV_ROOT */
> +#endif /* CONFIG_MSHV_ROOT && CONFIG_CRASH_DUMP */
>
> #else /* CONFIG_HYPERV */
> static inline void hyperv_init(void) {}
>
> Michael
Thanks. Yeah, either of the above two is ok. The latter does not
duplicate, so may be tiny bit better. Wei will pick one and apply
directly.
Thanks,
-Mukesh
next prev parent reply other threads:[~2025-10-20 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 22:42 [PATCH v3 0/6] Hyper-V: Implement hypervisor core collection Mukesh Rathor
2025-10-06 22:42 ` [PATCH v3 1/6] x86/hyperv: Rename guest crash shutdown function Mukesh Rathor
2025-10-06 22:42 ` [PATCH v3 2/6] hyperv: Add two new hypercall numbers to guest ABI public header Mukesh Rathor
2025-10-06 22:42 ` [PATCH v3 3/6] hyperv: Add definitions for hypervisor crash dump support Mukesh Rathor
2025-10-06 22:42 ` [PATCH v3 4/6] x86/hyperv: Add trampoline asm code to transition from hypervisor Mukesh Rathor
2025-10-06 22:42 ` [PATCH v3 5/6] x86/hyperv: Implement hypervisor RAM collection into vmcore Mukesh Rathor
2026-01-13 11:14 ` Borislav Petkov
2026-01-13 23:36 ` Mukesh R
2025-10-06 22:42 ` [PATCH v3 6/6] x86/hyperv: Enable build of hypervisor crashdump collection files Mukesh Rathor
2025-10-17 22:33 ` [PATCH v3 0/6] Hyper-V: Implement hypervisor core collection Wei Liu
2025-10-17 22:57 ` Wei Liu
2025-10-17 23:58 ` Mukesh R
2025-10-18 2:54 ` Michael Kelley
2025-10-20 19:05 ` Mukesh R [this message]
2025-10-20 20:48 ` Wei Liu
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=4a4fa302-18fa-ba01-ec06-d4bf0cc84032@linux.microsoft.com \
--to=mrathor@linux.microsoft.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--cc=x86@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