On 05/08/15 20:51, Laszlo Ersek wrote: > My SMM-for-OVMF branch has 52 patches now, and I'm not seeing the light > at the end of the tunnel. It's probably prudent to flush some > preparatory patches now that should be fine / non-controversial in their > own right. > > Public branch: https://github.com/lersek/edk2/commits/bits_and_pieces > > Thanks > Laszlo > > Laszlo Ersek (11): > OvmfPkg: split Include/OvmfPlatforms.h > OvmfPkg: consolidate POWER_MGMT_REGISTER_Q35() on "Q35MchIch9.h" > macros > OvmfPkg: consolidate POWER_MGMT_REGISTER_PIIX4() on "I440FxPiix4.h" > macros > OvmfPkg: extract some bits and port offsets common to Q35 and I440FX > OvmfPkg: AcpiS3SaveDxe: fix protocol usage hint in the INF file > MdePkg: BaseExtractGuidedSectionLib: allow forced reinit of handler > table > MdeModulePkg: SmmIplEntry(): don't suppress SMM core startup failure > UefiCpuPkg: CpuDxe: optionally save MTRR settings to AcpiNVS memory > block > UefiCpuPkg: CpuDxe: broadcast MTRR changes to APs > UefiCpuPkg: CpuDxe: sync MTRR settings to APs at MP startup > UefiCpuPkg: CpuDxe: provide EFI_MP_SERVICES_PROTOCOL when there's no > AP
Patches 01 to 05 have been committed as r17432 to r17437, inclusive; splitting up 01/11 as Jordan suggested. I'm retracting patch 06 for now; I've moved it back to its original place in my larger series. The reason is that I'm now convinced that such patches (outside of OvmfPkg/) can be best argued for when they are shown in the larger feature context (ie. how I'm going to rely on them), so I'll delay patch 06 until I send out the large-ish series. Patch 07 has been committed as SVN r17417. The commit message was not kept intact (there's a copy/paste typo in it, plus it was rewrapped), but it's not too grave, luckily. Regarding the UefiCpuPkg patches 08 through 11, inclusive, I'm postponing those too -- same treatment as for 06. I've picked up Jeff Fan's R-b tags for patches 10 and 11; those will be present when I include these UefiCpuPkg patches next time. This should also give us more time to research the 2-clause BSDL vs. 3-clause BSDL question and if Intel can relicense the original Quark package under the 2-clause BSDL. So, if there's still someone reviewing this prep series (beyond the licensing question above): please feel free to abandon it now. Thanks Laszlo ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
