Hi,
> Are you talking about the same posix test suite that LSB is using? I've
> looked into that a little, but here are the two problems I'm wanting to
> address:
>
> 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 ca
> To: Paul Larson/Austin/IBM@ibmus
> cc:
> Subject: Re: Kernel stress testing coverage
>
> >One thing I've been using for coverage (at least some coverage) is the
>
> posix
>
> >test suite
>
> --
>
> Are you talking about th
> 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 inte
Alan Cox <[EMAIL PROTECTED]> on 03/08/2001 02:06:06 PM
To: Paul Larson/Austin/IBM@ibmus
cc:
Subject: Re: Kernel stress testing coverage
>One thing I've been using for coverage (at least some coverage) is the
posix
>test suite
--
Are you talki
[EMAIL PROTECTED] said:
> I've heard of tools like gcov for doing this with applications, but
> the kernel itself seems like it might require something more.
Have a look at user-mode Linux (http://user-mode-linux.sourceforge.net). It
runs the kernel in userspace, so gprof and gcov can be used
5 matches
Mail list logo
