From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Zan Lynx <zlynx@acm.org>, Thomas Gleixner <tglx@linutronix.de>,
Len Brown <lenb@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: echo mem > /sys/power/state
Date: Fri, 18 Jan 2008 15:26:15 +0100 [thread overview]
Message-ID: <200801181526.16967.rjw@sisk.pl> (raw)
In-Reply-To: <20080118121803.GF11044@elte.hu>
On Friday, 18 of January 2008, Ingo Molnar wrote:
>
> * Andrew Morton <akpm@linux-foundation.org> 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
next prev parent reply other threads:[~2008-01-18 14:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 6:24 echo mem > /sys/power/state Andrew Morton
2008-01-17 17:36 ` Zan Lynx
2008-01-17 19:13 ` Andrew Morton
2008-01-17 21:38 ` Rafael J. Wysocki
2008-01-17 21:45 ` Nigel Cunningham
2008-01-17 22:27 ` Rafael J. Wysocki
2008-01-18 8:36 ` Ingo Molnar
2008-01-18 8:47 ` Andrew Morton
2008-01-18 9:04 ` Harvey Harrison
2008-01-18 12:18 ` Ingo Molnar
2008-01-18 14:26 ` Rafael J. Wysocki [this message]
2008-01-20 23:39 ` Pavel Machek
2008-01-20 23:42 ` Ingo Molnar
2008-01-21 0:31 ` Pavel Machek
2008-01-21 2:13 ` Johannes Weiner
2008-01-21 22:37 ` Pavel Machek
2008-01-22 14:42 ` Ingo Molnar
2008-01-23 21:27 ` Pavel Machek
2008-01-17 21:48 ` Jiri Slaby
2008-01-18 8:51 ` Ingo Molnar
2008-01-17 18:22 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801181526.16967.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=zlynx@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).