linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Guo, Min" <min.guo@intel.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: About test suites for linux hot plug
Date: Mon, 02 Dec 2002 00:59:29 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-103879130125378@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103838709921894@msgid-missing>

Thank you very much!

-----Original Message-----
From: Scott Murray [mailto:scottm@somanetworks.com]
Sent: Saturday, November 30, 2002 5:25 AM
To: Guo, Min
Cc: Linux-hotplug-devel@lists.sourceforge.net
Subject: RE: About test suites for linux hot plug


On Thu, 28 Nov 2002, Guo, Min wrote:

> Here is my initial test suite  for cPCI (ZT5084 platform) and Compaq with
> e100 and e1000 hotplug network devices,
> for the other hot plug device and features, I will give out the test
suites
> later. 

Your testcase seems reasonable, but having the PCI device appear/disappear 
is IMO the trivial part of PCI hotplug.  The vast majority of the problems
I encountered while writing the cPCI drivers involved PCI resources.  Most 
of my manual testing revolves around checking the contents of /proc/iomem 
and /proc/ioports before and after inserts and removes, as well as looking 
at the output of "lspci -vvv".  With a fixed set of hardware, it may be 
possible to come up with testcases for resource allocation, but the general
case is probably difficult to automate.

[Guo,Min] Thank you for your kind suggestion, I will investigate and try to
realize such 
function.

Something else to be aware of is that eventually I plan to support 
hardware that does not expose HS_CSR through the PCI extended capabilities.
It looks like your testcase as it stands now will break if run in a setup
that had such hardware. 

[Guo Min]: I will take a look at the platform and revise my test cases,
thank you very much!

Scott

PS: Are you working with Harold Yang?  He's also at Intel but seems to be
    having troubles using cPCI hotplug on his ZT5084 system.

[Guo Min]: Yes, I thought he had  already solved the problems.


-- 
Scott Murray
SOMA Networks, Inc.
Toronto, Ontario
e-mail: scottm@somanetworks.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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

  parent reply	other threads:[~2002-12-02  0:59 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
2002-11-28 12:52 ` Guo, Min
2002-11-29 21:24 ` Scott Murray
2002-12-02  0:59 ` Guo, Min [this message]
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-103879130125378@msgid-missing \
    --to=min.guo@intel.com \
    --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).