From: Alexey Makhalov <alexey.makhalov@broadcom.com>
To: x86@kernel.org, virtualization@lists.linux.dev, bp@alien8.de,
hpa@zytor.com, dave.hansen@linux.intel.com, mingo@redhat.com,
tglx@linutronix.de
Cc: ajay.kaher@broadcom.com, brennan.lamoreaux@broadcom.com,
bo.gan@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org, kas@kernel.org,
rick.p.edgecombe@intel.com, linux-coco@lists.linux.dev
Subject: Re: [PATCH v2 0/4] x86/vmware: Hypercall refactoring and improved guest support
Date: Mon, 18 May 2026 15:52:21 -0700 [thread overview]
Message-ID: <70843c91-b1f7-4f5b-9960-43390df6dd2d@broadcom.com> (raw)
In-Reply-To: <20260309235250.2611115-1-alexey.makhalov@broadcom.com>
On 3/9/26 4:52 PM, Alexey Makhalov wrote:
> This series improves VMware guest support on x86 by refactoring the
> hypercall infrastructure and adding better crash diagnostics, along
> with encrypted guest support for the steal time clock.
>
> The first patch introduces a common vmware_hypercall() backend selected
> via static calls. It consolidates the existing hypercall mechanisms
> (backdoor, VMCALL/VMMCALL, and TDX) behind a single interface and
> selects the optimal implementation at boot. This reduces duplication
> and simplifies future extensions.
>
> Building on top of the new hypercall infrastructure, the next two
> patches improve post-mortem debugging of VMware guests. They export
> panic information to the hypervisor by dumping kernel messages to the
> VM vmware.log on the host and explicitly reporting guest crash event
> to the hypervisor.
>
> The final patch adds support for encrypted guests by ensuring that the
> shared memory used for the steal time clock is mapped as decrypted
> before being shared with the hypervisor. This enables steal time
> accounting to function correctly when guest memory encryption is
> enabled.
>
> Patch overview:
>
> 1. x86/vmware: Introduce common vmware_hypercall
>
> * Consolidate hypercall implementations behind a common API
> * Select backend via static_call at boot
>
> 2. x86/vmware: Log kmsg dump on panic
>
> * Register a kmsg dumper
> * Export panic logs to the host
>
> 3. x86/vmware: Report guest crash to the hypervisor
>
> * Register a panic notifier
> * Notify the hypervisor about guest crashes
>
> 4. x86/vmware: Support steal time clock for encrypted guests
>
> * Mark shared steal time memory as decrypted early in boot
>
>
> Changelog:
>
> V1 -> V2
> * Fix compilation warnings in patch 2 "x86/vmware: Log kmsg dump on panic"
> reported by kernel test robot <lkp@intel.com>
>
>
> Alexey Makhalov (4):
> x86/vmware: Introduce common vmware_hypercall()
> x86/vmware: Log kmsg dump on panic
> x86/vmware: Report guest crash to the hypervisor
> x86/vmware: Support steal time clock for encrypted guests
>
> arch/x86/include/asm/vmware.h | 276 ++++++++------------
> arch/x86/kernel/cpu/vmware.c | 470 +++++++++++++++++++++++++---------
> 2 files changed, 463 insertions(+), 283 deletions(-)
>
>
> base-commit: 7d08a6ad25f85c9bb7d0382142838cb54713f1a3
Gentle reminder to review this change. Thanks,
--Alexey
prev parent reply other threads:[~2026-05-18 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 0:42 [PATCH 0/4] x86/vmware: Hypercall refactoring and improved guest support Alexey Makhalov
2026-03-07 0:42 ` [PATCH 1/4] x86/vmware: Introduce common vmware_hypercall() Alexey Makhalov
2026-03-07 0:42 ` [PATCH 2/4] x86/vmware: Log kmsg dump on panic Alexey Makhalov
2026-03-07 12:03 ` kernel test robot
2026-03-07 13:26 ` kernel test robot
2026-03-07 0:42 ` [PATCH 3/4] x86/vmware: Report guest crash to the hypervisor Alexey Makhalov
2026-03-07 0:42 ` [PATCH 4/4] x86/vmware: Support steal time clock for encrypted guests Alexey Makhalov
2026-03-09 23:52 ` [PATCH v2 0/4] x86/vmware: Hypercall refactoring and improved guest support Alexey Makhalov
2026-03-09 23:52 ` [PATCH v2 1/4] x86/vmware: Introduce common vmware_hypercall() Alexey Makhalov
2026-03-09 23:52 ` [PATCH v2 2/4] x86/vmware: Log kmsg dump on panic Alexey Makhalov
2026-03-09 23:52 ` [PATCH v2 3/4] x86/vmware: Report guest crash to the hypervisor Alexey Makhalov
2026-03-09 23:52 ` [PATCH v2 4/4] x86/vmware: Support steal time clock for encrypted guests Alexey Makhalov
2026-05-18 22:52 ` Alexey Makhalov [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=70843c91-b1f7-4f5b-9960-43390df6dd2d@broadcom.com \
--to=alexey.makhalov@broadcom.com \
--cc=ajay.kaher@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bo.gan@broadcom.com \
--cc=bp@alien8.de \
--cc=brennan.lamoreaux@broadcom.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux.dev \
--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