From: Dionna Amalie Glaze <dionnaglaze@google.com>
To: Peter Gonda <pgonda@google.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Tom Lendacky <Thomas.Lendacky@amd.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Joerg Roedel <jroedel@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH v5 0/4] Add throttling detection to sev-guest
Date: Thu, 3 Nov 2022 12:03:39 -0700 [thread overview]
Message-ID: <CAAH4kHaPzwKsyV7XuKEDS6Q7WsC0+mNz4hsp=MW9n1Pc3=KtrA@mail.gmail.com> (raw)
In-Reply-To: <CAMkAt6pRVnx3vHkeBeJuf5kHgTF+c3Ydir+r9MRCPMAXic5eog@mail.gmail.com>
> Should this change be rebased on top of the 'virt: sev: Prevent IV
> reuse in SNP guest driver'?
> https://lore.kernel.org/lkml/20221103152318.88354-1-pgonda@google.com/
>
> Since that change is a security fix?
I can do that when your patch gets its Reviewed-By tags.
--
-Dionna Glaze, PhD (she/her)
prev parent reply other threads:[~2022-11-03 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 15:18 [PATCH v5 0/4] Add throttling detection to sev-guest Dionna Glaze
2022-11-02 15:18 ` [PATCH v5 1/4] ccp: Name -1 return value as SEV_RET_NO_FW_CALL Dionna Glaze
2022-11-02 17:30 ` Tom Lendacky
2022-11-02 18:46 ` Borislav Petkov
2022-11-02 15:18 ` [PATCH v5 2/4] x86/sev: Change snp_guest_issue_request's fw_err Dionna Glaze
2022-11-02 15:18 ` [PATCH v5 3/4] virt/coco/sev-guest: Remove err in handle_guest_request Dionna Glaze
2022-11-02 15:18 ` [PATCH v5 4/4] virt/coco/sev-guest: interpret VMM errors from guest request Dionna Glaze
2022-11-03 15:26 ` [PATCH v5 0/4] Add throttling detection to sev-guest Peter Gonda
2022-11-03 19:03 ` Dionna Amalie Glaze [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='CAAH4kHaPzwKsyV7XuKEDS6Q7WsC0+mNz4hsp=MW9n1Pc3=KtrA@mail.gmail.com' \
--to=dionnaglaze@google.com \
--cc=Thomas.Lendacky@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=tglx@linutronix.de \
--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 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.