From: "Brijesh Singh" <brijesh.singh@amd.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: brijesh.singh@amd.com, James Bottomley <jejb@linux.ibm.com>,
"Xu, Min M" <min.m.xu@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Laszlo Ersek <lersek@redhat.com>,
Erdem Aktas <erdemaktas@google.com>
Subject: Re: [edk2-devel] [PATCH 0/3] Move the SEV specific changes in ResetVector in separate file
Date: Tue, 27 Jul 2021 06:46:55 -0500 [thread overview]
Message-ID: <92b03856-d644-6141-a02d-349ec2907195@amd.com> (raw)
In-Reply-To: <PH0PR11MB4885120FBAC0644C15A9C3978CE99@PH0PR11MB4885.namprd11.prod.outlook.com>
On 7/27/21 6:30 AM, Yao, Jiewen wrote:
> Thank you Brijesh. That is exactly what I want.
>
> Reviewed-by: Jiewen Yao <Jiewen.yao@intel.com>
>
> Sorry, I obviously overlooked the SNP series.
>
> If you don't mind, I would like to merge this at first as soon as possible, then we can build up more stuff on top it.
I am good with merging if all other reviewers are fine with it. I did
tested both the SEV, SEV-ES, non-SEV to make sure nothing is broken
after the refactor.
thanks
next prev parent reply other threads:[~2021-07-27 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 11:16 [PATCH 0/3] Move the SEV specific changes in ResetVector in separate file Brijesh Singh
2021-07-27 11:16 ` [PATCH 1/3] OvmfPkg/ResetVector: move SEV specific code in a " Brijesh Singh
2021-07-27 13:43 ` Lendacky, Thomas
2021-07-27 11:16 ` [PATCH 2/3] OvmfPkg/ResetVector: add the macro to invoke MSR protocol based VMGEXIT Brijesh Singh
2021-07-27 11:16 ` [PATCH 3/3] OvmfPkg/ResetVector: add the macro to request guest termination Brijesh Singh
2021-07-27 11:30 ` [edk2-devel] [PATCH 0/3] Move the SEV specific changes in ResetVector in separate file Yao, Jiewen
2021-07-27 11:46 ` Brijesh Singh [this message]
2021-07-27 11:54 ` Yao, Jiewen
2021-07-27 12:12 ` Ard Biesheuvel
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-list 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=92b03856-d644-6141-a02d-349ec2907195@amd.com \
--to=devel@edk2.groups.io \
/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