Basically, it is similar to AFDOUpdateEbuildStage, which modifies Chrome ebuilds.
Steps:
1. Refactor AFDOUpdateEbuildStage into AFDOUpdateChromeEbuildStage and so on. Factor the common parts out.
2. Implement AFDOUpdateKernelEbuildStage.
3. Unittests.
I'm going to disable kernel_afdo on daisy because of this:
https://bugs.chromium.org/p/chromium/issues/detail?id=772450
We are pretty unlucky because we just disabled it two weeks ago and re-enabled it on Oct. 4. My guess is that compiler inlined slightly more aggressively due to the new profiles.
Unfortunately, it seems that we don't have other armv7 boards other than 3.8 or 3.10 or rk3288.
Comment 1 by bugdroid1@chromium.org
, Sep 26 2017