On Wed, Jan 23, 2019 at 09:32:16PM -0500, Joel Fernandes wrote: > On Wed, Jan 23, 2019 at 02:37:47PM -0800, Daniel Colascione wrote: > > On Wed, Jan 23, 2019 at 1:29 PM Karim Yaghmour > > <karim.yaghmour@xxxxxxxxxxx> wrote: > [...] > > > Personally I advocated a more aggressive approach with Joel in private: > > > just put the darn headers straight into the kernel image, it's the > > > *only* artifact we're sure will follow the Android device whatever > > > happens to it (like built-in ftrace). > > > > I was thinking along similar lines. Ordinarily, we make loadable > > kernel modules. What we kind of want here is a non-loadable kernel > > module --- or a non-loadable section in the kernel image proper. I'm > > not familiar with early-stage kernel loader operation: I know it's > > possible to crease discardable sections in the kernel image, but can > > we create sections that are never slurped into memory in the first > > place? If not, maybe loading and immediately discarding the header > > section is good enough. > > I am happy to see if I can shrink it down further. Especially using xz and > stripping all comments period. I am optimistic this can be brought down > further to a point where it would make sense to everyone to build it into the > kernel. Lets see. > > Last time I stripped comments, it went down by ~40%. What I haven't tried is > doing this *with* xz compression. I am also open to brainstorming what else > can be stripped. Removing comments (/* */) with xz compression brings it down to 3.3MB. thanks, - Joel
