From: Wei Liu <wei.liu@kernel.org>
To: Anirudh Rayabharam <anrayabh@linux.microsoft.com>
Cc: Saurabh Sengar <ssengar@linux.microsoft.com>,
ssengar@microsoft.com, kys@microsoft.com, haiyangz@microsoft.com,
wei.liu@kernel.org, decui@microsoft.com,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
mikelley@microsoft.com, tglx@linutronix.de, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com
Subject: Re: [PATCH v2] x86/Hyper-V: Expand definition of struct hv_vp_assist_page
Date: Fri, 11 Nov 2022 23:39:31 +0000 [thread overview]
Message-ID: <Y27dM1z+QphRFgMi@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <Y2je48OwQaRTkci+@anrayabh-desk>
On Mon, Nov 07, 2022 at 04:03:07PM +0530, Anirudh Rayabharam wrote:
> On Fri, Nov 04, 2022 at 11:38:43AM -0700, Saurabh Sengar wrote:
> > The struct hv_vp_assist_page has 24 bytes which is defined as u64[3],
> > expand that to expose vtl_entry_reason, vtl_ret_x64rax and vtl_ret_x64rcx
> > field. vtl_entry_reason is updated by hypervisor for the entry reason as
> > to why the VTL was entered on the virtual processor.
> > Guest updates the vtl_ret_* fields to provide the register values to
> > restore on VTL return. The specific register values that are restored
> > which will be updated on vtl_ret_x64rax and vtl_ret_x64rcx.
> > Also added the missing fields for synthetic_time_unhalted_timer_expired,
> > virtualization_fault_information and intercept_message.
I did a bit of stylistic changes to the commit message and queued this
up to hyperv-next. Thanks.
prev parent reply other threads:[~2022-11-11 23:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 18:38 [PATCH v2] x86/Hyper-V: Expand definition of struct hv_vp_assist_page Saurabh Sengar
2022-11-07 10:33 ` Anirudh Rayabharam
2022-11-11 23:39 ` 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=Y27dM1z+QphRFgMi@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=anrayabh@linux.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=mikelley@microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@microsoft.com \
--cc=tglx@linutronix.de \
--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