- 20 Jun, 2005 34 commits
-
-
mochel@digitalimplant.org authored
This klist interface provides a couple of structures that wrap around struct list_head to provide explicit list "head" (struct klist) and list "node" (struct klist_node) objects. For struct klist, a spinlock is included that protects access to the actual list itself. struct klist_node provides a pointer to the klist that owns it and a kref reference count that indicates the number of current users of that node in the list. The entire point is to provide an interface for iterating over a list that is safe and allows for modification of the list during the iteration (e.g. insertion and removal), including modification of the current node on the list. It works using a 3rd object type - struct klist_iter - that is declared and initialized before an iteration. klist_next() is used to acquire the next element in the list. It returns NULL if there are no more items. This klist interface provides a couple of structures that wrap around struct list_head to provide explicit list "head" (struct klist) and list "node" (struct klist_node) objects. For struct klist, a spinlock is included that protects access to the actual list itself. struct klist_node provides a pointer to the klist that owns it and a kref reference count that indicates the number of current users of that node in the list. The entire point is to provide an interface for iterating over a list that is safe and allows for modification of the list during the iteration (e.g. insertion and removal), including modification of the current node on the list. It works using a 3rd object type - struct klist_iter - that is declared and initialized before an iteration. klist_next() is used to acquire the next element in the list. It returns NULL if there are no more items. Internally, that routine takes the klist's lock, decrements the reference count of the previous klist_node and increments the count of the next klist_node. It then drops the lock and returns. There are primitives for adding and removing nodes to/from a klist. When deleting, klist_del() will simply decrement the reference count. Only when the count goes to 0 is the node removed from the list. klist_remove() will try to delete the node from the list and block until it is actually removed. This is useful for objects (like devices) that have been removed from the system and must be freed (but must wait until all accessors have finished). Internally, that routine takes the klist's lock, decrements the reference count of the previous klist_node and increments the count of the next klist_node. It then drops the lock and returns. There are primitives for adding and removing nodes to/from a klist. When deleting, klist_del() will simply decrement the reference count. Only when the count goes to 0 is the node removed from the list. klist_remove() will try to delete the node from the list and block until it is actually removed. This is useful for objects (like devices) that have been removed from the system and must be freed (but must wait until all accessors have finished). Signed-off-by:
Patrick Mochel <mochel@digitalimplant.org> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de> diff -Nru a/include/linux/klist.h b/include/linux/klist.h
-
mochel@digitalimplant.org authored
Signed-off-by:
-
mochel@digitalimplant.org authored
Signed-off-by:
-
mochel@digitalimplant.org authored
Now there's an iterator for accessing each device bound to a driver. Signed-off-by:
-
mochel@digitalimplant.org authored
This relocates the driver binding/unbinding code to drivers/base/dd.c. This is done for two reasons: One, it's not code related to the bus_type itself; it uses some from that, some from devices, and some from drivers. And Two, it will make it easier to do some of the upcoming lock removal on that code.. Signed-off-by:
-
mochel@digitalimplant.org authored
This adds a per-device semaphore that is taken before every call from the core to a driver method. This prevents e.g. simultaneous calls to the ->suspend() or ->resume() and ->probe() or ->release(), potentially saving a whole lot of headaches. It also moves us a step closer to removing the bus rwsem, since it protects the fields in struct device that are modified by the core. Signed-off-by:
-
Andrew Morton authored
Cc: Corey Minyard <minyard@acm.org> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
Adrian Bunk authored
Due to the removal of class_simple.c, "make mandocs" no longer works. This patch fixes this issue. Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
Mark M. Hoffman authored
Trivial fix to USB class-creation error path; please apply. Signed-off-by:
Mark M. Hoffman <mhoffman@lightlink.com> Signed-off-by:
-
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
This moves a kref into the main hcd structure, which detaches it from the class device structure. Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
Signed-off-by: -
gregkh@suse.de authored
One step on improving the class api so that it can not be used incorrectly. This also fixes the module owner issue with the dev files that happened when the devt logic moved to the class core. Based on a patch originally written by Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: -
Dmitry Torokhov authored
sysfs: fix the rest of the kernel so if an attribute doesn't implement show or store method read/write will return -EIO instead of 0 or -EINVAL or -EPERM. Signed-off-by:Dmitry Torokhov <dtor@mail.ru> Signed-off-by:
-
Dmitry Torokhov authored
sysfs: fix drivers/block so if an attribute doesn't implement show or store method read/write will return -EIO instead of 0 or -EINVAL. Signed-off-by: -
Dmitry Torokhov authored
sysfs: fix drivers/pci so if an attribute does not implement show or store method read/write will return -EIO instead of 0. Signed-off-by: -
Dmitry Torokhov authored
sysfs: fix drivers/base so if an attribute doesn't implement show or store method read/write will return -EIO instead of 0. Signed-off-by: -
Dmitry Torokhov authored
sysfs: if attribute does not implement show or store method read/write should return -EIO instead of 0 or -EINVAL. Signed-off-by: -
Dmitry Torokhov authored
sysfs: make attributes and attribute_group's names const char * Signed-off-by:
-
Dmitry Torokhov authored
Driver core: change driver's, bus's, class's and platform device's names to be const char * so one can use const char *drv_name = "asdfg"; when initializing structures. Also kill couple of whitespaces. Signed-off-by: -
Dmitry Torokhov authored
kobject: change name() method in kset_hotplug_ops return const char * since users shoudl not try to modify returned data. Signed-off-by:
-
Dmitry Torokhov authored
kobject: make kobject's name const char * since users should not attempt to change it (except by calling kobject_rename). Signed-off-by:
-
Dmitry Torokhov authored
sysfs: make sysfs_{create|remove}_link to take const char * name. Signed-off-by: -
Dmitry Torokhov authored
kobject: kobject_hotplug should use kobject_name() instead of accessing kobj->name directly since for objects with long names it can contain garbage. Signed-off-by:
-
- 19 Jun, 2005 6 commits
-
-
Linus Torvalds authored
-
Russell King authored
-
Russell King authored
We need to re-initialise the stack pointers for undefined, IRQ and abort mode handlers whenever we resume. Signed-off-by:Russell King <rmk+kernel@arm.linux.org.uk>
-
Russell King authored
Add missed new files from basic SMP support for the Integrator/CP platform. Signed-off-by: -
David S. Miller authored
When enabled, this should disable UCOPY prequeue'ing altogether, but it does not due to a missing test. Signed-off-by:David S. Miller <davem@davemloft.net>
-
Jesper Juhl authored
This patch changes the type of the third parameter 'length' of the raw_send_hdrinc() function from 'int' to 'size_t'. This makes sense since this function is only ever called from one location, and the value passed as the third parameter in that location is itself of type size_t, so this makes the recieving functions parameter type match. Also, inside raw_send_hdrinc() the 'length' variable is used in comparisons with unsigned values and passed as parameter to functions expecting unsigned values (it's used in a single comparison with a signed value, but that one can never actually be negative so the patch also casts that one to size_t to stop gcc worrying, and it is passed in a single instance to memcpy_fromiovecend() which expects a signed int, but as far as I can see that's not a problem since the value of 'length' shouldn't ever exceed the value of a signed int). Signed-off-by:
Jesper Juhl <juhl-lkml@dif.dk> Signed-off-by:
-
