public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Lendacky, Thomas" <thomas.lendacky@amd.com>
To: gaoliming <gaoliming@byosoft.com.cn>,
	devel@edk2.groups.io, lersek@redhat.com,
	'Ray Ni' <ray.ni@intel.com>, "'Dong, Eric'" <eric.dong@intel.com>,
	'Michael D Kinney' <michael.d.kinney@intel.com>
Cc: 'Brijesh Singh' <brijesh.singh@amd.com>,
	'Zhiguang Liu' <zhiguang.liu@intel.com>,
	'Jordan Justen' <jordan.l.justen@intel.com>,
	'Ard Biesheuvel' <ard.biesheuvel@arm.com>
Subject: Re: 回复: 回复: [edk2-devel] 回复: 回复: 回复: [PATCH v2 01/11] MdePkg, OvmfPkg: Clean up GHCB field offsets and save area
Date: Mon, 26 Oct 2020 11:34:14 -0500	[thread overview]
Message-ID: <7a298343-a73d-ac5a-af90-a58ad9e97937@amd.com> (raw)
In-Reply-To: <000401d6a8e8$4b15d790$e14186b0$@byosoft.com.cn>

On 10/22/20 9:57 PM, gaoliming wrote:
> Laszlo:
>  I agree Bisectability is important. I want to consider the impact and balance the change. Now, this change will update UefiCpuPkg. I also want to collect the feedback from UefiCpuPkg maintainer: Ray and Eric. 

Ray/Eric,

Any feedback on this question (specifically for patch #10 of this series,
not this patch)? I'd also prefer to maintain bisectability and therefore
submit the changes to the UefiCpuPkg and OvmfPkg in the same patch.

Thanks,
Tom

> 
> Thanks
> Liming
>> -----邮件原件-----
>> 发件人: bounce+27952+66536+4905953+8761045@groups.io
>> <bounce+27952+66536+4905953+8761045@groups.io> 代表 Laszlo Ersek
>> 发送时间: 2020年10月22日 21:13
>> 收件人: gaoliming <gaoliming@byosoft.com.cn>; devel@edk2.groups.io;
>> thomas.lendacky@amd.com
>> 抄送: 'Brijesh Singh' <brijesh.singh@amd.com>; 'Michael D Kinney'
>> <michael.d.kinney@intel.com>; 'Zhiguang Liu' <zhiguang.liu@intel.com>;
>> 'Jordan Justen' <jordan.l.justen@intel.com>; 'Ard Biesheuvel'
>> <ard.biesheuvel@arm.com>
>> 主题: Re: 回复: [edk2-devel] 回复: 回复: 回复: [PATCH v2 01/11] MdePkg,
>> OvmfPkg: Clean up GHCB field offsets and save area
>>
>> On 10/22/20 03:25, gaoliming wrote:
>>> Tom:
>>>   For the patch in UefiCpuPkg, this changes the library interface. So, the
>> consumer and producer code is required to be changed together. There is no
>> good compatible way to do it. I still prefer to separate them for the different
>> package. Although the first commit breaks the tree, your patch is the patch
>> serial, they will be merged together. Its impact should be small.
>>
>> I really disagree here. Bisectability is way more important, in my
>> opinion, than avoiding a multi-package patch.
>>
>> I agree we should avoid multi-package patches as much as we can -- but
>> not more than we can. Bisectability (= keeping the tree buildable at
>> every commit) is very important, in my opinion.
>>
>> Thanks,
>> Laszlo
>>
>>
>>
>> 
>>
> 
> 
> 

  reply	other threads:[~2020-10-26 16:34 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 16:09 [PATCH v2 00/11] SEV-ES guest support fixes and cleanup Lendacky, Thomas
2020-10-16 16:09 ` [PATCH v2 01/11] MdePkg, OvmfPkg: Clean up GHCB field offsets and save area Lendacky, Thomas
2020-10-19  1:41   ` 回复: " gaoliming
2020-10-19 12:50     ` Lendacky, Thomas
2020-10-19 20:17       ` Laszlo Ersek
2020-10-19 20:48         ` Lendacky, Thomas
2020-10-19 20:42       ` Laszlo Ersek
2020-10-20  1:08         ` 回复: " gaoliming
2020-10-20  8:31           ` Laszlo Ersek
2020-10-20 13:10             ` Lendacky, Thomas
2020-10-21  0:54               ` 回复: " gaoliming
2020-10-21 21:54                 ` Lendacky, Thomas
2020-10-22  1:25                   ` 回复: [edk2-devel] " gaoliming
2020-10-22 13:12                     ` Laszlo Ersek
2020-10-23  2:57                       ` 回复: " gaoliming
2020-10-26 16:34                         ` Lendacky, Thomas [this message]
2020-10-27  7:57                           ` Dong, Eric
2020-10-28 17:42                             ` Lendacky, Thomas
2020-10-21 12:29               ` Laszlo Ersek
2020-10-16 16:09 ` [PATCH v2 02/11] UefiCpuPkg/VmgExitLib: Add interfaces to set/read GHCB ValidBitmap bits Lendacky, Thomas
2020-10-19 20:46   ` [edk2-devel] " Laszlo Ersek
2020-10-16 16:09 ` [PATCH v2 03/11] OvmfPkg/VmgExitLib: Implement new VmgExitLib interfaces Lendacky, Thomas
2020-10-19 20:51   ` [edk2-devel] " Laszlo Ersek
2020-10-16 16:09 ` [PATCH v2 04/11] OvmfPkg/VmgExitLib: Set the SW exit fields when performing VMGEXIT Lendacky, Thomas
2020-10-19 20:53   ` [edk2-devel] " Laszlo Ersek
2020-10-16 16:09 ` [PATCH v2 05/11] OvmfPkg/VmgExitLib: Set the SwScratch valid bit for IOIO events Lendacky, Thomas
2020-10-19 20:54   ` [edk2-devel] " Laszlo Ersek
2020-10-16 16:09 ` [PATCH v2 06/11] OvmfPkg/VmgExitLib: Set the SwScratch valid bit for MMIO events Lendacky, Thomas
2020-10-16 16:09 ` [PATCH v2 07/11] UefiCpuPkg/MpInitLib: Set the SW exit fields when performing VMGEXIT Lendacky, Thomas
2020-10-16 16:09 ` [PATCH v2 08/11] OvmfPkg/QemuFlashFvbServicesRuntimeDxe: Set the SwScratch valid bit Lendacky, Thomas
2020-10-19 20:57   ` [edk2-devel] " Laszlo Ersek
2020-10-16 16:09 ` [PATCH v2 09/11] OvmfPkg/QemuFlashFvbServicesRuntimeDxe: Fix erase blocks for SEV-ES Lendacky, Thomas
2020-10-16 16:09 ` [PATCH v2 10/11] UefiCpuPkg, OvmfPkg: Disable interrupts when using the GHCB Lendacky, Thomas
2020-10-19 21:07   ` [edk2-devel] " Laszlo Ersek
2020-10-16 16:09 ` [PATCH v2 11/11] UefiCpuPkg/MpInitLib: For SEV-ES guest, set stack based on processor number Lendacky, Thomas

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=7a298343-a73d-ac5a-af90-a58ad9e97937@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