From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: About test suites for linux hot plug
Date: Wed, 27 Nov 2002 19:38:37 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103842594802885@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103838709921894@msgid-missing>
>> Thanks for your perfect work! I am interested in the Linux hot swap
>>project and now doing some validation work about the compactPCI hot
>>swap. So could you please tell me whether there are some test suites
>>for linux hot plug, if not, I'd like to write some test suites for the
>>project!
To the extent that such tests cover things like verifying that streams
of hotplug events are handled consistently, the latest CVS does have a
simple facility to log events to files like /var/log/hotplug/pci.events
(for CardBus, cPCI, hotplugPCI, etc) or /var/log/hotplug/events (for any
event that doesn't have an agent enabled).
So you can collect hotplug events "live", and then (by writing simple
software) play them back later ... Or just notice what kinds of hotplug
events don't yet have /etc/hotplug/*.agent code.
I hope that facility will evolve -- and not primarily for testing support.
For example, I'd be interested in seeing some daemon thread monitoring
/var/log/hotplug/input.events that's set up as a named fifo, as one way to
solve hotplug's "need multiple security domains" issue. (That's an area
where anyone who's familiar with those user mode APIs could contribute
useful "seed" code in C, or likely even Perl ...)
> If you take a look at the archives for this list, you will see we just
> talked about this with another intel employee (who you also copied on
> the message) :)
>
> In short, no there aren't any. Also, this is probably the wrong list
> for cPCI hotplug specific stuff.
But any test scripts you put together that are general purpose would
likely help down the line. Both automated "do these events get handled
correctly" scripts, and manual "plug in the adapter and verify that
these N things got set up right".
- Dave
-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2002-11-27 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 8:44 About test suites for linux hot plug Guo, Min
2002-11-27 16:32 ` Greg KH
2002-11-27 19:38 ` David Brownell [this message]
2002-11-28 12:52 ` Guo, Min
2002-11-29 21:24 ` Scott Murray
2002-12-02 0:59 ` Guo, Min
2002-12-26 7:32 ` Guo, Min
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=marc-linux-hotplug-103842594802885@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@vger.kernel.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).