From: "Huang, Kai" <kai.huang@intel.com>
To: "pbonzini@redhat.com" <pbonzini@redhat.com>,
"seanjc@google.com" <seanjc@google.com>,
"nikunj@amd.com" <nikunj@amd.com>
Cc: "thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
"santosh.shukla@amd.com" <santosh.shukla@amd.com>,
"bp@alien8.de" <bp@alien8.de>
Subject: Re: [RFC PATCH 2/4] KVM: SEV: Skip SNP-safe allocation when HvInUseWrAllowed is supported
Date: Wed, 27 Aug 2025 09:54:55 +0000 [thread overview]
Message-ID: <d3f9c3f09fbbe2523329c57c0c911ac8afc9c2b8.camel@intel.com> (raw)
In-Reply-To: <eef0e010-181b-491d-9b5e-91bc35bf566c@amd.com>
On Tue, 2025-08-26 at 20:37 +0530, Nikunj A. Dadhania wrote:
>
> On 8/26/2025 3:37 PM, Huang, Kai wrote:
> > On Mon, 2025-08-25 at 15:20 +0000, Nikunj A Dadhania wrote:
> > > When HvInUseWrAllowed (CPUID 8000001F EAX[30]) is supported, the CPU allows
> > > hypervisor writes to in-use pages without RMP violations, making the 2MB
> > > alignment workaround unnecessary. Check for this capability to avoid the
> > > allocation overhead when it's not needed.
> >
> > Could you add some text to explain why this is related to PML?
>
> PML works fine without this and the change is not linked to PML. This can go
> as a separate fix.
I suppose it's better to send it out as a separate one if PML doesn't need
it to work.
next prev parent reply other threads:[~2025-08-27 9:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 15:20 [RFC PATCH 0/4] KVM: SVM: Add Page Modification Logging (PML) support Nikunj A Dadhania
2025-08-25 15:20 ` [RFC PATCH 1/4] KVM: x86: Carve out PML flush routine Nikunj A Dadhania
2025-08-26 10:06 ` Huang, Kai
2025-08-26 14:58 ` Nikunj A. Dadhania
2025-08-27 9:53 ` Huang, Kai
2025-08-28 6:30 ` Nikunj A. Dadhania
2025-08-25 15:20 ` [RFC PATCH 2/4] KVM: SEV: Skip SNP-safe allocation when HvInUseWrAllowed is supported Nikunj A Dadhania
2025-08-26 10:07 ` Huang, Kai
2025-08-26 15:07 ` Nikunj A. Dadhania
2025-08-27 9:54 ` Huang, Kai [this message]
2025-08-25 15:20 ` [RFC PATCH 3/4] x86/cpufeatures: Add Page modification logging Nikunj A Dadhania
2025-08-25 15:25 ` Borislav Petkov
2025-08-25 15:20 ` [RFC PATCH 4/4] KVM: SVM: Add Page modification logging support Nikunj A Dadhania
2025-08-27 23:44 ` Huang, Kai
2025-08-28 6:37 ` Nikunj A. Dadhania
2025-08-28 10:33 ` Huang, Kai
2025-08-28 10:43 ` Nikunj A. Dadhania
2025-08-28 11:09 ` Huang, Kai
2025-08-28 11:17 ` Huang, Kai
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=d3f9c3f09fbbe2523329c57c0c911ac8afc9c2b8.camel@intel.com \
--to=kai.huang@intel.com \
--cc=bp@alien8.de \
--cc=joao.m.martins@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=santosh.shukla@amd.com \
--cc=seanjc@google.com \
--cc=thomas.lendacky@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.