From: Roman Kisel <romank@linux.microsoft.com>
To: Saurabh Singh Sengar <ssengar@linux.microsoft.com>,
Wei Liu <wei.liu@kernel.org>
Cc: bp@alien8.de, dave.hansen@linux.intel.com, decui@microsoft.com,
haiyangz@microsoft.com, hpa@zytor.com, kys@microsoft.com,
mingo@redhat.com, tglx@linutronix.de,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, apais@microsoft.com, benhill@microsoft.com,
sunilmut@microsoft.com, vdso@hexbites.dev
Subject: Re: [PATCH hyperv-next 0/2] x86/hyperv: VTL mode reboot fixes
Date: Wed, 12 Feb 2025 14:56:43 -0800 [thread overview]
Message-ID: <e39b1947-0ea6-4573-9b71-7c8ea6c96d8c@linux.microsoft.com> (raw)
In-Reply-To: <20250212175445.GA19243@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On 2/12/2025 9:54 AM, Saurabh Singh Sengar wrote:
> On Wed, Feb 12, 2025 at 02:21:18AM +0000, Wei Liu wrote:
[...]
>>
>> Saurabh please review these patches. Thanks.
>
> Hi Roman,
Hi Saurabh,
>
> Thanks for the patch, few suggestions and queries:
>
> 1. Please fix the kernel bot warning
Will do!
> 2. Cc Stable tree is not enough, you need to mention the "Fixes" tag as well
> for the commit upto where you want this patch to be backported.
Understood, thanks!
> 3. In your 2/2 commit, you mention 'triple fault' is the only way to reboot in x86.
> Is that accurate ? Do you mean to say OpenHCL/VTL here ?
> If this behaviour is specific to OpenHCl and not VTLs in general, is there a way
> we can make these changes only for OpenHCL.
Right, I meant OpenHCL/VTL2, thank you very much! The changes are scoped
to running in VTLs in general at the moment. I can add a check for the
VTL == 2 if you'd like me to.
For VTL1 (aka LVBS), maybe folks would like to do something else,
do you happen to know? Maybe to report that to the VTL0 guest kernel
although seems dubious: the higher VTL failed so the lights must be out
for the lower VTLs? Or kexec?
>
>
> - Saurabh
>
>>
>> I don't have a strong opinion on them.
>>
>>>
>>> arch/x86/hyperv/hv_vtl.c | 31 +++++++++++++++++++++++++++++++
>>> 1 file changed, 31 insertions(+)
>>>
>>>
>>> base-commit: 2e03358be78b65d28b66e17aca9e0c8700b0df78
>>> --
>>> 2.34.1
>>>
--
Thank you,
Roman
next prev parent reply other threads:[~2025-02-12 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 21:07 [PATCH hyperv-next 0/2] x86/hyperv: VTL mode reboot fixes Roman Kisel
2025-01-17 21:07 ` [PATCH hyperv-next 1/2] x86/hyperv: VTL mode emergency restart callback Roman Kisel
2025-01-17 21:07 ` [PATCH hyperv-next 2/2] x86/hyperv: VTL mode callback for restarting the system Roman Kisel
2025-01-18 16:19 ` kernel test robot
2025-02-12 2:21 ` [PATCH hyperv-next 0/2] x86/hyperv: VTL mode reboot fixes Wei Liu
2025-02-12 17:54 ` Saurabh Singh Sengar
2025-02-12 22:56 ` Roman Kisel [this message]
2025-02-13 10:52 ` Saurabh Singh Sengar
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=e39b1947-0ea6-4573-9b71-7c8ea6c96d8c@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=vdso@hexbites.dev \
--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