From: Wei Liu <wei.liu@kernel.org>
To: Mukesh R <mrathor@linux.microsoft.com>
Cc: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
wei.liu@kernel.org
Subject: Re: [PATCH v1] x86/hyperv: Move hv crash init after hypercall pg setup
Date: Wed, 4 Feb 2026 06:27:16 +0000 [thread overview]
Message-ID: <20260204062716.GH79272@liuwe-devbox-debian-v2.local> (raw)
In-Reply-To: <20260204015800.40843-1-mrathor@linux.microsoft.com>
On Tue, Feb 03, 2026 at 05:58:00PM -0800, Mukesh R wrote:
> hv_root_crash_init() is not setting up the hypervisor crash collection
> for baremetal cases because when it's called, hypervisor page is not
> setup.
> This got missed due to internal mirror falling behind.
This doesn't provide useful information for our future selves.
>
> Fix is simple, just move the crash init call after the hypercall
> page setup.
>
> Signed-off-by: Mukesh Rathor <mrathor@linux.microsoft.com>
Applied.
Wei
> ---
> arch/x86/hyperv/hv_init.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/hyperv/hv_init.c b/arch/x86/hyperv/hv_init.c
> index 14de43f4bc6c..7f3301bd081e 100644
> --- a/arch/x86/hyperv/hv_init.c
> +++ b/arch/x86/hyperv/hv_init.c
> @@ -558,7 +558,6 @@ void __init hyperv_init(void)
> memunmap(src);
>
> hv_remap_tsc_clocksource();
> - hv_root_crash_init();
> hv_sleep_notifiers_register();
> } else {
> hypercall_msr.guest_physical_address = vmalloc_to_pfn(hv_hypercall_pg);
> @@ -567,6 +566,9 @@ void __init hyperv_init(void)
>
> hv_set_hypercall_pg(hv_hypercall_pg);
>
> + if (hv_root_partition()) /* after set hypercall pg */
> + hv_root_crash_init();
> +
> skip_hypercall_pg_init:
> /*
> * hyperv_init() is called before LAPIC is initialized: see
> --
> 2.51.2.vfs.0.1
>
prev parent reply other threads:[~2026-02-04 6:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 1:58 [PATCH v1] x86/hyperv: Move hv crash init after hypercall pg setup Mukesh R
2026-02-04 6:27 ` Wei Liu [this message]
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=20260204062716.GH79272@liuwe-devbox-debian-v2.local \
--to=wei.liu@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrathor@linux.microsoft.com \
/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