From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, bob.c.feng@intel.com
Subject: Re: [edk2-devel] [Patch 0/9 V2] Enable multiple process AutoGen
Date: Mon, 22 Jul 2019 22:53:22 +0200 [thread overview]
Message-ID: <53eee516-c1e2-b97d-7375-dbf0871a64b8@redhat.com> (raw)
In-Reply-To: <20190722085100.20552-1-bob.c.feng@intel.com>
Bob,
On 07/22/19 10:50, Bob Feng wrote:
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1875
>
> In order to improve the build performance, we implemented
> multiple-processes AutoGen. This change will reduce 20% time
> for AutoGen phase.
>
> The design document can be got from:
> https://edk2.groups.io/g/devel/files/Designs/2019/0627/Multiple-thread-AutoGen.pdf
>
> This patch serial pass the build of Ovmf, MinKabylake, MinPurley, packages
> under Edk2 repository and intel client and server platforms.
>
> V2:
> 1. The first version missed autogen related commit
> from e812a812c1a0800c49e11507cb46222351520cc7. V2 add those commit
> back.
> 2. Move CreateAsBuildInf into AutoGenWorker process
> 3. Save GlobalVar_<platform guid>_<arch>.bin to build folder.
> 4. Regenerate patches based on master bb824f685d
whenever someone posts a patch set (brand new patch set, or v2, v3, ...
of a previously posted patch set), I suggest capturing a mailing list
URL in the TianoCore Bugzilla, as a new comment.
This way someone interested in the evolution of the feature can approach
the mailing list postings from the Bugzilla, and get links to all
versions ever posted.
I've done this for your v1 posting; please add the v2 and v3 links.
(NB this request is for everyone.)
Thanks
Laszlo
prev parent reply other threads:[~2019-07-22 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 8:50 [Patch 0/9 V2] Enable multiple process AutoGen Bob Feng
2019-07-22 8:50 ` [Patch 1/9 V2] BaseTools: Singleton the object to handle build conf file Bob Feng
2019-07-22 8:50 ` [Patch 2/9 V2] BaseTools: Split WorkspaceAutoGen._InitWorker into multiple functions Bob Feng
2019-07-22 8:50 ` [Patch 3/9 V2] BaseTools: Add functions to get platform scope build options Bob Feng
2019-07-22 8:50 ` [Patch 4/9 V2] BaseTools: Decouple AutoGen Objects Bob Feng
2019-07-22 8:50 ` [Patch 5/9 V2] BaseTools: Enable Multiple Process AutoGen Bob Feng
2019-07-22 8:50 ` [Patch 6/9 V2] BaseTools: Add shared data for processes Bob Feng
2019-07-22 8:50 ` [Patch 7/9 V2] BaseTools: Add LogAgent to support multiple process Autogen Bob Feng
2019-07-22 8:50 ` [Patch 8/9 V2] BaseTools: Move BuildOption parser out of build.py Bob Feng
2019-07-22 8:51 ` [Patch 9/9 V2] BaseTools: Add the support for python 2 Bob Feng
2019-07-22 20:53 ` Laszlo Ersek [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-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=53eee516-c1e2-b97d-7375-dbf0871a64b8@redhat.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