Re: echo mem > /sys/power/state

[Rafael J. Wysocki]

On Friday, 18 of January 2008, Ingo Molnar wrote:
> 
> * Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> > > (it doesnt matter if graphics does not resume fine - at least for my 
> > > tests)
> > > 
> > > kprobes had similar problems and it now has a few simple smoke-tests 
> > > - which i just saw trigger on a patch that i did not notice would 
> > > break kprobes. I think this should be done for all functionality 
> > > that is not regularly triggered by a normal distro bootup (and which 
> > > is easy to overlook in testing).
> > 
> > Seeing as we're so lame about being able to distribute userspace 
> > stuff: create a shell script in /proc/rc.kernel and start teaching 
> > initscripts to run it.  Then we can modify it at will.
> 
> would be fine to me.

Yes, that might work.

> The problem isnt just distribution and the tests
> getting out of sync with the kernel (and its capabilities enabled in the 
> .config, etc.), the other problem is unintrusive testing: i for example 
> use unmodified images of various distributions, with only a new bzImage 
> plopped in. That is an intentionally minimal impact test vector, any 
> userspace side changes are discouraged. And that's how many people test 
> new kernels, they just plop it in. The moment we require any userlevel 
> changes, the testing barrier increases significantly.

Very true.

Greetings,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/