From: Nikunj A Dadhania <nikunj@amd.com>
To: <seanjc@google.com>, <pbonzini@redhat.com>
Cc: <thomas.lendacky@amd.com>, <bp@alien8.de>,
<joao.m.martins@oracle.com>, <kai.huang@intel.com>,
<yosry@kernel.org>, <kvm@vger.kernel.org>
Subject: Re: [PATCH v8 0/8] KVM: SVM: Add Page Modification Logging (PML) support
Date: Tue, 29 Sep 2026 10:57:26 +0530 [thread overview]
Message-ID: <7911fb0b-5b8a-4a4d-8495-e82555fa0fd1@amd.com> (raw)
In-Reply-To: <20260907063906.1964557-1-nikunj@amd.com>
On 9/7/2026 12:08 PM, Nikunj A Dadhania wrote:
> This series implements Page Modification Logging (PML) for guests on select
> AMD Zen6 and later processors, bringing hardware-assisted dirty logging
> support. PML is designed to track guest modified memory pages. PML enables the> hypervisor to identify which pages in a guest's memory have been modified
> since the last checkpoint or during live migration. More details can be
> found in the latest AMD APM Volume 2 (System Programming), section
> "15.25.15 Page Modification Logging".
>
> The PML feature uses two new VMCB fields (PML_ADDR and PML_INDEX) and
> generates a VMEXIT when the 4KB log buffer becomes full.
>
> The feature is enabled by default when hardware support is detected and can
> be disabled via the 'pml' module parameter.
>
> Changelog:
> v8:
> * Rebased on latest kvm/next
> * Drop redundant pml_addr=0 in nested_vmcb02_prepare_control() (Yosry)
> * Fix misleading comment, pml_index=-1 is hardening not stale-data
> cleanup (Yosry, Sean)
> * Route nested SVM_EXIT_PML_FULL to KVM and treat it as unexpected
> exit (Sean)
> * Refactor update_cpu_dirty_logging() to common code as a separate
> pre-patch (Sean)
>
Hi Sean,
A gentle ping on this series. Is there anything else you would like me
to change, or does this look reasonable for v7.4?
Regards,
Nikunj
next prev parent reply other threads:[~2026-09-29 5:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:38 [PATCH v8 0/8] KVM: SVM: Add Page Modification Logging (PML) support Nikunj A Dadhania
2026-09-07 6:38 ` [PATCH v8 1/8] KVM: VMX: Pass @vcpu, not @vmx to init_vmcs() Nikunj A Dadhania
2026-09-07 6:39 ` [PATCH v8 2/8] KVM: x86: Move PML page to common vcpu arch structure Nikunj A Dadhania
2026-09-07 6:39 ` [PATCH v8 3/8] KVM: x86: Carve out PML flush routine Nikunj A Dadhania
2026-09-07 6:39 ` [PATCH v8 4/8] KVM: VMX: Use cpu_dirty_log_size instead of enable_pml for PML checks Nikunj A Dadhania
2026-09-07 6:39 ` [PATCH v8 5/8] KVM: x86: Carve out common dirty logging update Nikunj A Dadhania
2026-09-07 6:39 ` [PATCH v8 6/8] x86/cpufeatures: Add Page modification logging Nikunj A Dadhania
2026-09-07 6:47 ` sashiko-bot
2026-09-07 9:49 ` Nikunj A. Dadhania
2026-09-07 6:39 ` [PATCH v8 7/8] KVM: SVM: Use BIT_ULL for 64-bit misc_ctl bit definitions Nikunj A Dadhania
2026-09-07 6:39 ` [PATCH v8 8/8] KVM: SVM: Add Page modification logging support Nikunj A Dadhania
2026-09-07 7:00 ` sashiko-bot
2026-09-08 4:08 ` Nikunj A. Dadhania
2026-09-10 0:22 ` Sean Christopherson
2026-09-21 5:23 ` Nikunj A. Dadhania
2026-09-29 5:27 ` Nikunj A Dadhania [this message]
2026-10-02 21:07 ` [PATCH v8 0/8] KVM: SVM: Add Page Modification Logging (PML) support Sean Christopherson
2026-10-05 3:31 ` Nikunj A. Dadhania
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=7911fb0b-5b8a-4a4d-8495-e82555fa0fd1@amd.com \
--to=nikunj@amd.com \
--cc=bp@alien8.de \
--cc=joao.m.martins@oracle.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
--cc=yosry@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