[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b5c82c21-fef5-4ddb-bc0f-d0d5d89e5a5d@linux.microsoft.com>
Date: Mon, 27 Oct 2025 14:13:36 -0700
From: Easwar Hariharan <easwar.hariharan@...ux.microsoft.com>
To: Praveen K Paladugu <prapal@...ux.microsoft.com>
Cc: easwar.hariharan@...ux.microsoft.com, kys@...rosoft.com,
haiyangz@...rosoft.com, wei.liu@...nel.org, decui@...rosoft.com,
tglx@...utronix.de, mingo@...hat.com, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, bp@...en8.de, dave.hansen@...ux.intel.com,
x86@...nel.org, hpa@...or.com, arnd@...db.de, anbelski@...ux.microsoft.com,
nunodasneves@...ux.microsoft.com, skinsburskii@...ux.microsoft.com
Subject: Re: [PATCH v3 0/2] Add support for clean shutdown with MSHV
On 10/27/2025 2:11 PM, Praveen K Paladugu wrote:
>
>
> On 10/27/2025 3:56 PM, Easwar Hariharan wrote:
>> On 10/27/2025 1:28 PM, Praveen K Paladugu wrote:
>>> Add support for clean shutdown of the root partition when running on MSHV
>>> hypervisor.
>>>
>>> v3:
>>> - Dropped acpi_sleep handlers as they are not used on mshv
>>> - Applied ordering for hv_reboot_notifier
>>> - Fixed build issues on i386, arm64 architectures
>>>
>>> v2:
>>> - Addressed review comments from v1.
>>> - Moved all sleep state handling methods under CONFIG_ACPI stub
>>> - - This fixes build issues on non-x86 architectures.
>>>
>>> Praveen K Paladugu (2):
>>> hyperv: Add definitions for MSHV sleep state configuration
>>> hyperv: Enable clean shutdown for root partition with MSHV
>>>
>>> arch/x86/hyperv/hv_init.c | 8 +++
>>> arch/x86/include/asm/mshyperv.h | 2 +
>>> drivers/hv/mshv_common.c | 103 ++++++++++++++++++++++++++++++++
>>> include/hyperv/hvgdk_mini.h | 4 +-
>>> include/hyperv/hvhdk_mini.h | 33 ++++++++++
>>> 5 files changed, 149 insertions(+), 1 deletion(-)
>>>
>>
>> This series seems to assume that Mukesh's hypervisor crash series has been merged, but that's not the case.
>> I don't see any code context or logical dependency on that series, but correct me if I'm wrong. If there's no
>> dependency, can you send a v4 based on Linus' tree or hyperv-next to avoid a merge conflict?
>>
>
> I rebased this patchset on top of hyperv/hyperv-next branch, which has crashdump patches: https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/log/?h=hyperv-next
>
> Let me know if I missed/misunderstood anything.
>
Nope, a miss on my part. Sorry about the noise.
Thanks,
Easwar (he/him)
Powered by blists - more mailing lists