John Levon wrote: > Has someone thought through the implications of the IPS approach on > the CTF parts of the kernel build? (See > http://blogs.sun.com/levon/entry/reducing_ctf_overhead if you need > context)
From the referenced blog: > For the sake of kmdb and crash dumps, the CTF data for each kernel > binary is present in the memory image of a booted kernel. Since the ctf data is present in the in memory portion of the elf files, it is part of the elf hash and thus any file w/ varying cft data should be part of the new package(s). There are distinct implications of CTF on the number of binaries changed in each build; this will need to be explored. If necessary, we may need to work on making the CTF construction process more deterministic. - Bart -- Bart Smaalders Solaris Kernel Performance [EMAIL PROTECTED] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
