From: Roman Kisel <romank@linux.microsoft.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, decui@microsoft.com,
haiyangz@microsoft.com, hpa@zytor.com, kys@microsoft.com,
mingo@redhat.com, ssengar@linux.microsoft.com,
tglx@linutronix.de, wei.liu@kernel.org, x86@kernel.org,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: apais@microsoft.com, benhill@microsoft.com, sunilmut@microsoft.com
Subject: [PATCH hyperv-next v3 0/2] x86/hyperv: VTL mode reboot fixes
Date: Thu, 27 Feb 2025 13:47:26 -0800 [thread overview]
Message-ID: <20250227214728.15672-1-romank@linux.microsoft.com> (raw)
The first patch defines a specialized machine emergency restart
callback not to write to the physical address of 0x472 which is
what the native_machine_emergency_restart() does unconditionally.
I first wanted to tweak that function[1], and in the course of
the discussion it looked as the risks of doing that would
outweigh the benefit: the bare-metal systems have likely adopted
that behavior as a standard although I could not find any mentions
of that magic address in the UEFI+ACPI specification.
The second patch removes the need to always supply "reboot=t"
to the kernel command line in the OpenHCL bootloader[2]. There is
no other option at the moment; when/if it appears the newly added
callback's code can be adjusted as required.
[1] https://lore.kernel.org/all/20250109204352.1720337-1-romank@linux.microsoft.com/
[2] https://github.com/microsoft/openvmm/blob/7a9d0e0a00461be6e5f3267af9ea54cc7157c900/openhcl/openhcl_boot/src/main.rs#L139
[V3]:
- Added verbs to the patch titles.
** Thank you, Ingo!**
[V2]: https://lore.kernel.org/linux-hyperv/97010881-4b5e-4fb7-b8b3-b6c9e440e692@linux.microsoft.com/
- Fixed the warning from the kernel robot about using C23.
** Thank you, kernel robot!**
- Tightened up wording in the comments and the commit
descriptions.
** Thank you, Saurabh!**
- Dropped the CC: stable tag as there is no specific commit
this patch series fixes.
** Thank you, Saurabh!**
[V1]: https://lore.kernel.org/linux-hyperv/20250117210702.1529580-1-romank@linux.microsoft.com/
Roman Kisel (2):
x86/hyperv: Add VTL mode emergency restart callback
x86/hyperv: Add VTL mode callback for restarting the system
arch/x86/hyperv/hv_vtl.c | 34 ++++++++++++++++++++++++++++++++++
1 file changed, 34 insertions(+)
base-commit: 3a7f7785eae7cf012af128ca9e383c91e4955354
--
2.43.0
next reply other threads:[~2025-02-27 21:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 21:47 Roman Kisel [this message]
2025-02-27 21:47 ` [PATCH hyperv-next v3 1/2] x86/hyperv: Add VTL mode emergency restart callback Roman Kisel
2025-02-27 21:47 ` [PATCH hyperv-next v3 2/2] x86/hyperv: Add VTL mode callback for restarting the system Roman Kisel
2025-03-11 21:57 ` [PATCH hyperv-next v3 0/2] x86/hyperv: VTL mode reboot fixes 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=20250227214728.15672-1-romank@linux.microsoft.com \
--to=romank@linux.microsoft.com \
--cc=apais@microsoft.com \
--cc=benhill@microsoft.com \
--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-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ssengar@linux.microsoft.com \
--cc=sunilmut@microsoft.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;
as well as URLs for NNTP newsgroup(s).