| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <466919FB.8080204@s5r6.in-berlin.de> Date: Fri, 08 Jun 2007 10:57:31 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: "Huang, Ying" <ying.huang@...el.com> CC: linux-kernel@...r.kernel.org Subject: Re: [PATCH] driver core: multithreaded device matching with dependency Huang, Ying wrote: > This is another solution to implement multithreaded device matching > (probing). The device matching is delayed until all drivers are > registered. The driver registering is executed one by one, this > eliminates the potential of interdependency between driver. All devices > are matched to drivers afterwards, multithreaded. The parent <-> > children relationship between devices is used as the dependency between > devices, that is, the children devices matching will not begin until > parent device matching finishes. How can subsystems control multithreaded vs. singlethreaded probes? For example, the IEEE 1394 subsystem should probe different nodes in parallel, but different units on the same node serially. Similar requirements exist with other hardware. Also, how can subsystems enable and disable multithreaded probes? ... > +EXPORT_SYMBOL_GPL(device_match_freeze); > +EXPORT_SYMBOL_GPL(device_match_thaw); Their definitions lack kerneldoc comments. -- Stefan Richter -=====-=-=== -==- -=--- http://arcgraph.de/sr/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists