linux-coco.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dionna Amalie Glaze <dionnaglaze@google.com>
To: Ashish Kalra <Ashish.Kalra@amd.com>
Cc: seanjc@google.com, pbonzini@redhat.com, tglx@linutronix.de,
	 mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org,  hpa@zytor.com, thomas.lendacky@amd.com,
	john.allen@amd.com,  herbert@gondor.apana.org.au,
	davem@davemloft.net, michael.roth@amd.com,  kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux-crypto@vger.kernel.org,
	linux-coco@lists.linux.dev
Subject: Re: [PATCH v3 4/7] crypto: ccp: Register SNP panic notifier only if SNP is enabled
Date: Mon, 6 Jan 2025 11:08:39 -0800	[thread overview]
Message-ID: <CAAH4kHaiU8W7zb5oEWghrHTC2XvC4e__cD+6pYMprH9c=iddUA@mail.gmail.com> (raw)
In-Reply-To: <674affc649968994f95b6259f162d5f0732b102c.1735931639.git.ashish.kalra@amd.com>

On Fri, Jan 3, 2025 at 12:01 PM Ashish Kalra <Ashish.Kalra@amd.com> wrote:
>
> From: Ashish Kalra <ashish.kalra@amd.com>
>
> Register the SNP panic notifier if and only if SNP is actually
> initialized and deregistering the notifier when shutting down
> SNP in PSP driver when KVM module is unloaded.
>
> Currently the SNP panic notifier is being registered
> irrespective of SNP being enabled/initialized and with this
> change the SNP panic notifier is registered only if SNP
> support is enabled and initialized.
>
> Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>

Reviewed-by: Dionna Glaze <dionnaglaze@google.com>

-- 
-Dionna Glaze, PhD, CISSP, CCSP (she/her)

  reply	other threads:[~2025-01-06 19:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03 19:58 [PATCH v3 0/7] Move initializing SEV/SNP functionality to KVM Ashish Kalra
2025-01-03 19:59 ` [PATCH v3 1/7] crypto: ccp: Move dev_info/err messages for SEV/SNP initialization Ashish Kalra
2025-01-06 17:17   ` Dionna Amalie Glaze
2025-01-06 23:08     ` Kalra, Ashish
2025-01-07 14:29   ` Tom Lendacky
2025-01-03 20:00 ` [PATCH v3 2/7] crypto: ccp: Fix implicit SEV/SNP init and shutdown in ioctls Ashish Kalra
2025-01-06 18:01   ` Dionna Amalie Glaze
2025-01-06 23:48     ` Kalra, Ashish
2025-01-07 19:08       ` Kalra, Ashish
2025-01-07  3:29   ` Alexey Kardashevskiy
2025-01-07 18:53     ` Kalra, Ashish
2025-01-03 20:00 ` [PATCH v3 3/7] crypto: ccp: Reset TMR size at SNP Shutdown Ashish Kalra
2025-01-03 20:00 ` [PATCH v3 4/7] crypto: ccp: Register SNP panic notifier only if SNP is enabled Ashish Kalra
2025-01-06 19:08   ` Dionna Amalie Glaze [this message]
2025-01-03 20:01 ` [PATCH v3 5/7] crypto: ccp: Add new SEV/SNP platform shutdown API Ashish Kalra
2025-01-06 19:14   ` Dionna Amalie Glaze
2025-01-03 20:01 ` [PATCH v3 6/7] KVM: SVM: Add support to initialize SEV/SNP functionality in KVM Ashish Kalra
2025-01-07 16:42   ` Tom Lendacky
2025-01-07 18:34     ` Kalra, Ashish
2025-01-07 20:56       ` Kalra, Ashish
2025-01-08 17:22       ` Tom Lendacky
2025-01-09  0:27         ` Kalra, Ashish
2025-01-10 22:41           ` Kalra, Ashish
2025-01-11  0:40             ` Sean Christopherson
2025-01-11  0:41               ` Dionna Amalie Glaze
2025-01-11  0:49                 ` Sean Christopherson
2025-01-13 15:03               ` Kalra, Ashish
2025-01-14 21:14                 ` Kalra, Ashish
2025-01-14 22:31                   ` Sean Christopherson
2025-01-15 22:26                     ` Kalra, Ashish
2025-01-03 20:02 ` [PATCH v3 7/7] crypto: ccp: Move SEV/SNP Platform initialization to KVM Ashish Kalra

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='CAAH4kHaiU8W7zb5oEWghrHTC2XvC4e__cD+6pYMprH9c=iddUA@mail.gmail.com' \
    --to=dionnaglaze@google.com \
    --cc=Ashish.Kalra@amd.com \
    --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-coco@lists.linux.dev \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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;
as well as URLs for NNTP newsgroup(s).