From: "Ashish Kalra" <ashish.kalra@amd.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: devel@edk2.groups.io, brijesh.singh@amd.com,
Thomas.Lendacky@amd.com, jejb@linux.ibm.com,
erdemaktas@google.com, jiewen.yao@intel.com, min.m.xu@intel.com,
jordan.l.justen@intel.com, ard.biesheuvel@arm.com,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v4 0/4] SEV Live Migration support for OVMF.
Date: Wed, 23 Jun 2021 17:03:40 +0000 [thread overview]
Message-ID: <20210623170340.GA8387@ashkalra_ubuntu_server> (raw)
In-Reply-To: <48675290-6ad7-6ca0-0ff6-4fe60366ed72@redhat.com>
Hello Laszlo,
Yes i will file a TianoCore Feature Request BZ for this and i am working
on a v5 for this patch-set.
Thanks,
Ashish
On Wed, Jun 23, 2021 at 06:49:06PM +0200, Laszlo Ersek wrote:
> On 06/23/21 18:42, Laszlo Ersek wrote:
> > On 06/22/21 19:46, Ashish Kalra wrote:
>
> >> Please find below your reply on v3 of this patch-set :
> >>
> >> Please include such a patch in v4 -- if Tom and Brijesh agree, I'd like to put the new lib explicitly under their reviewership.
> >>
> >> Also, I plan to review this series (v4, at this point) only for formalities. I'd like to receive an R-b from Tom or Brijesh [*], and another from Dov or a colleague at IBM, for this series; those together should suffice for merging the library.
> >>
> >> So, if you are fine with this approach, then probably Tom or Brijesh can
> >> take these patches under their reviewership and provide their R-b for
> >> this patch-set to be accepted and merged.
> >
> > Indeed. This helps. Thanks.
> >
> > I'll keep this patch set in my review queue then, for said "formalities
> > review".
>
> Please do file a TianoCore Feature Request BZ for this, and reference
> the bug URL in the commit messages. One important purpose of such a BZ
> is to succinctly link together all versions of a patch set -- that way
> poor maintainers know where to find previous versions, even if the blurb
> subject line changes over time. I also like to capture "permanent
> workflow notes" like the above in BZs (basically a high-level summary of
> who does what).
>
> For now it seems that a v5 will be necessary. Please keep me on CC, and
> when you have the BZ filed, we should link all past and future versions
> into it.
>
> Thanks
> Laszlo
>
next prev parent reply other threads:[~2021-06-23 17:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 13:56 [PATCH v4 0/4] SEV Live Migration support for OVMF Ashish Kalra
2021-06-21 13:56 ` [PATCH v4 1/4] OvmfPkg/MemEncryptHypercallLib: add library to support SEV hypercalls Ashish Kalra
2021-06-22 19:47 ` Brijesh Singh
2021-06-22 19:58 ` Brijesh Singh
2021-06-22 22:47 ` Lendacky, Thomas
2021-06-22 23:20 ` Ashish Kalra
2021-06-22 23:38 ` Brijesh Singh
2021-06-23 1:47 ` Ashish Kalra
2021-06-23 15:02 ` Ashish Kalra
2021-06-21 13:57 ` [PATCH v4 2/4] OvmfPkg/BaseMemEncryptLib: Support to issue unencrypted hypercall Ashish Kalra
2021-06-22 22:50 ` Lendacky, Thomas
2021-06-21 13:57 ` [PATCH v4 3/4] OvmfPkg/PlatformPei: Mark SEC GHCB page as unencrypted via hypercall Ashish Kalra
2021-06-22 20:35 ` Brijesh Singh
2021-06-21 13:57 ` [PATCH v4 4/4] OvmfPkg/PlatformDxe: Add support for SEV live migration Ashish Kalra
2021-06-22 23:06 ` Lendacky, Thomas
2021-06-24 16:29 ` Ashish Kalra
2021-06-22 17:20 ` [PATCH v4 0/4] SEV Live Migration support for OVMF Laszlo Ersek
2021-06-22 17:45 ` Brijesh Singh
2021-06-22 17:46 ` Ashish Kalra
2021-06-23 13:18 ` [edk2-devel] " Dov Murik
2021-06-23 16:42 ` Laszlo Ersek
2021-06-23 16:49 ` Laszlo Ersek
2021-06-23 17:03 ` Ashish Kalra [this message]
2021-06-30 9:11 ` Ashish Kalra
2021-06-30 16:25 ` [edk2-devel] " Laszlo Ersek
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=20210623170340.GA8387@ashkalra_ubuntu_server \
--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