public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Ashish Kalra <Ashish.Kalra@amd.com>,
	tglx@linutronix.de, mingo@redhat.com,
	 dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
	 pbonzini@redhat.com, thomas.lendacky@amd.com,
	herbert@gondor.apana.org.au,  nikunj@amd.com,
	davem@davemloft.net, aik@amd.com, ardb@kernel.org,
	 john.allen@amd.com, michael.roth@amd.com,
	Neeraj.Upadhyay@amd.com,  linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org,  linux-crypto@vger.kernel.org
Subject: Re: [PATCH v4 1/3] x86/sev: Add new dump_rmp parameter to snp_leak_pages() API
Date: Fri, 12 Sep 2025 11:34:45 -0700	[thread overview]
Message-ID: <aMRnxb68UTzId7zz@google.com> (raw)
In-Reply-To: <20250912155852.GBaMRDPEhr2hbAXavs@fat_crate.local>

On Fri, Sep 12, 2025, Borislav Petkov wrote:
> On Wed, Sep 10, 2025 at 10:55:24PM +0000, Ashish Kalra wrote:
> > From: Ashish Kalra <ashish.kalra@amd.com>
> > 
> > When leaking certain page types, such as Hypervisor Fixed (HV_FIXED)
> > pages, it does not make sense to dump RMP contents for the 2MB range of
> > the page(s) being leaked. In the case of HV_FIXED pages, this is not an
> > error situation where the surrounding 2MB page RMP entries can provide
> > debug information.
> > 
> > Add new __snp_leak_pages() API with dump_rmp bool parameter to support
> > continue adding pages to the snp_leaked_pages_list but not issue
> > dump_rmpentry().
> > 
> > Make snp_leak_pages() a wrapper for the common case which also allows
> > existing users to continue to dump RMP entries.
> > 
> > Suggested-by: Thomas Lendacky <Thomas.Lendacky@amd.com>
> > Suggested-by: Sean Christopherson <seanjc@google.com>
> > Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
> > ---
> >  arch/x86/include/asm/sev.h | 8 +++++++-
> >  arch/x86/virt/svm/sev.c    | 7 ++++---
> >  2 files changed, 11 insertions(+), 4 deletions(-)
> 
> Sean, lemme know if I should carry this through tip.

Take them through tip, but the stubs mess in sev.h really needs to be cleaned up
(doesn't have to block this series, but should be done sooner than later).

  reply	other threads:[~2025-09-12 18:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10 22:55 [PATCH v4 0/3] crypto: ccp - Add AMD Seamless Firmware Servicing (SFS) driver Ashish Kalra
2025-09-10 22:55 ` [PATCH v4 1/3] x86/sev: Add new dump_rmp parameter to snp_leak_pages() API Ashish Kalra
2025-09-12 14:52   ` Tom Lendacky
2025-09-12 15:58   ` Borislav Petkov
2025-09-12 18:34     ` Sean Christopherson [this message]
2025-09-13 10:55       ` Borislav Petkov
2025-09-16  3:51         ` Herbert Xu
2025-09-16 10:27           ` Borislav Petkov
2025-09-12 18:34   ` Sean Christopherson
2025-09-12 19:37     ` Tom Lendacky
2025-09-12 19:41       ` Sean Christopherson
2025-09-12 19:52         ` Tom Lendacky
2025-09-10 22:55 ` [PATCH v4 2/3] crypto: ccp - Add new HV-Fixed page allocation/free API Ashish Kalra
2025-09-12 14:57   ` Tom Lendacky
2025-09-10 22:55 ` [PATCH v4 3/3] crypto: ccp - Add AMD Seamless Firmware Servicing (SFS) driver Ashish Kalra
2025-09-12 15:49   ` Tom Lendacky

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=aMRnxb68UTzId7zz@google.com \
    --to=seanjc@google.com \
    --cc=Ashish.Kalra@amd.com \
    --cc=Neeraj.Upadhyay@amd.com \
    --cc=aik@amd.com \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=hpa@zytor.com \
    --cc=john.allen@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=mingo@redhat.com \
    --cc=nikunj@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --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