> 1. How much of the kernel is getting hit on a run of any given test? Even
> an approximate percentage is fine as long as I can prove it.
I've not measured it by percentage. You could use the profiling code in
the kernel to generate a profile and from that measure coverage at least
for non interrupt blocking code
> piece of the kernel that they modified. These type of things would be
> FYI this project will be going on sourceforge very soon. I want to have a
> little more to start out with though and finish putting together a good
> project description, testplans, etc. to post as soon as we put it on there.
> I hate it when people start projects and you don't see any good information
> about it for weeks.
VA Cerberus has mahy of these
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
