From: Borislav Petkov <bp@alien8.de>
To: Dionna Glaze <dionnaglaze@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>, Peter Gonda <pgonda@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH v9 0/4] Add throttling detection to sev-guest
Date: Mon, 2 Jan 2023 17:10:38 +0100 [thread overview]
Message-ID: <Y7MB/kEHlsaAeAJM@zn.tnic> (raw)
In-Reply-To: <20221207010210.2563293-1-dionnaglaze@google.com>
Hi,
On Wed, Dec 07, 2022 at 01:02:06AM +0000, Dionna Glaze wrote:
> Dionna Glaze (3):
> x86/sev: Change snp_guest_issue_request's fw_err
> virt: sev-guest: Remove err in handle_guest_request
> virt: sev-guest: interpret VMM errors from guest request
>
> Peter Gonda (1):
> crypto: ccp - Name -1 return value as SEV_RET_NO_FW_CALL
can you please rebase those ontop of 6.2-rc2?
They conflict with Peter's IV reuse patch which is already upstream.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2023-01-02 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 1:02 [PATCH v9 0/4] Add throttling detection to sev-guest Dionna Glaze
2022-12-07 1:02 ` [PATCH v9 1/4] crypto: ccp - Name -1 return value as SEV_RET_NO_FW_CALL Dionna Glaze
2022-12-22 15:31 ` Borislav Petkov
2022-12-26 14:26 ` Tom Lendacky
2023-03-21 15:28 ` [tip: x86/sev] " tip-bot2 for Peter Gonda
2022-12-07 1:02 ` [PATCH v9 2/4] x86/sev: Change snp_guest_issue_request's fw_err Dionna Glaze
2022-12-07 1:02 ` [PATCH v9 3/4] virt: sev-guest: Remove err in handle_guest_request Dionna Glaze
2022-12-07 1:02 ` [PATCH v9 4/4] virt: sev-guest: interpret VMM errors from guest request Dionna Glaze
2023-01-02 16:10 ` Borislav Petkov [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=Y7MB/kEHlsaAeAJM@zn.tnic \
--to=bp@alien8.de \
--cc=Thomas.Lendacky@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=dionnaglaze@google.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.