)]}' { "log": [ { "commit": "8bb7844286fb8c9fce6f65d8288aeb09d03a5e0d", "tree": "f4e305edaedbde05774bb1e4acd89a9475661d2e", "parents": [ "f37bc2712b54ec641e0c0c8634f1a4b61d9956c0" ], "author": { "name": "Rafael J. Wysocki", "email": "rjw@sisk.pl", "time": "Wed May 09 02:35:10 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed May 09 12:30:56 2007 -0700" }, "message": "Add suspend-related notifications for CPU hotplug\n\nSince nonboot CPUs are now disabled after tasks and devices have been\nfrozen and the CPU hotplug infrastructure is used for this purpose, we need\nspecial CPU hotplug notifications that will help the CPU-hotplug-aware\nsubsystems distinguish normal CPU hotplug events from CPU hotplug events\nrelated to a system-wide suspend or resume operation in progress. This\npatch introduces such notifications and causes them to be used during\nsuspend and resume transitions. It also changes all of the\nCPU-hotplug-aware subsystems to take these notifications into consideration\n(for now they are handled in the same way as the corresponding \"normal\"\nones).\n\n[oleg@tv-sign.ru: cleanups]\nSigned-off-by: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\nCc: Gautham R Shenoy \u003cego@in.ibm.com\u003e\nCc: Pavel Machek \u003cpavel@ucw.cz\u003e\nSigned-off-by: Oleg Nesterov \u003coleg@tv-sign.ru\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "baaca49f415b25fdbe2a8f3c22b39929e450fbfd", "tree": "b152b4235fc07fe56619bd3a2e975e5ca90b8c5b", "parents": [ "6f7cc11aa6c7d5002e16096c7590944daece70ed" ], "author": { "name": "Gautham R Shenoy", "email": "ego@in.ibm.com", "time": "Wed May 09 02:34:03 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed May 09 12:30:51 2007 -0700" }, "message": "Define and use new events,CPU_LOCK_ACQUIRE and CPU_LOCK_RELEASE\n\nThis is an attempt to provide an alternate mechanism for postponing\na hotplug event instead of using a global mechanism like lock_cpu_hotplug.\n\nThe proposal is to add two new events namely CPU_LOCK_ACQUIRE and\nCPU_LOCK_RELEASE. The notification for these two events would be sent\nout before and after a cpu_hotplug event respectively.\n\nDuring the CPU_LOCK_ACQUIRE event, a cpu-hotplug-aware subsystem is\nsupposed to acquire any per-subsystem hotcpu mutex ( Eg. workqueue_mutex\nin kernel/workqueue.c ).\n\nDuring the CPU_LOCK_RELEASE release event the cpu-hotplug-aware subsystem\nis supposed to release the per-subsystem hotcpu mutex.\n\nThe reasons for defining new events as opposed to reusing the existing events\nlike CPU_UP_PREPARE/CPU_UP_FAILED/CPU_ONLINE for locking/unlocking of\nper-subsystem hotcpu mutexes are as follow:\n\n\t- CPU_LOCK_ACQUIRE: All hotcpu mutexes are taken before subsystems\n\tstart handling pre-hotplug events like CPU_UP_PREPARE/CPU_DOWN_PREPARE\n\tetc, thus ensuring a clean handling of these events.\n\n\t- CPU_LOCK_RELEASE: The hotcpu mutexes will be released only after\n\tall subsystems have handled post-hotplug events like CPU_DOWN_FAILED,\n\tCPU_DEAD,CPU_ONLINE etc thereby ensuring that there are no subsequent\n\tclashes amongst the interdependent subsystems after a cpu hotplugs.\n\nThis patch also uses __raw_notifier_call chain in _cpu_up to take care\nof the dependency between the two consequetive calls to\nraw_notifier_call_chain.\n\n[akpm@linux-foundation.org: fix a bug]\nSigned-off-by: Gautham R Shenoy \u003cego@in.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "6f7cc11aa6c7d5002e16096c7590944daece70ed", "tree": "68a11e4b67189c44ac0f3ab579e52e134d479cf5", "parents": [ "7c9cb38302e78d24e37f7d8a2ea7eed4ae5f2fa7" ], "author": { "name": "Gautham R Shenoy", "email": "ego@in.ibm.com", "time": "Wed May 09 02:34:02 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed May 09 12:30:51 2007 -0700" }, "message": "Extend notifier_call_chain to count nr_calls made\n\nSince 2.6.18-something, the community has been bugged by the problem to\nprovide a clean and a stable mechanism to postpone a cpu-hotplug event as\nlock_cpu_hotplug was badly broken.\n\nThis is another proposal towards solving that problem. This one is along the\nlines of the solution provided in kernel/workqueue.c\n\nInstead of having a global mechanism like lock_cpu_hotplug, we allow the\nsubsytems to define their own per-subsystem hot cpu mutexes. These would be\ntaken(released) where ever we are currently calling\nlock_cpu_hotplug(unlock_cpu_hotplug).\n\nAlso, in the per-subsystem hotcpu callback function,we take this mutex before\nwe handle any pre-cpu-hotplug events and release it once we finish handling\nthe post-cpu-hotplug events. A standard means for doing this has been\nprovided in [PATCH 2/4] and demonstrated in [PATCH 3/4].\n\nThe ordering of these per-subsystem mutexes might still prove to be a\nproblem, but hopefully lockdep should help us get out of that muddle.\n\nThe patch set to be applied against linux-2.6.19-rc5 is as follows:\n\n[PATCH 1/4] :\tExtend notifier_call_chain with an option to specify the\n\t\tnumber of notifications to be sent and also count the\n\t\tnumber of notifications actually sent.\n\n[PATCH 2/4] :\tDefine events CPU_LOCK_ACQUIRE and CPU_LOCK_RELEASE\n\t\tand send out notifications for these in _cpu_up and\n\t\t_cpu_down. This would help us standardise the acquire and\n\t\trelease of the subsystem locks in the hotcpu\n\t\tcallback functions of these subsystems.\n\n[PATCH 3/4] :\tEliminate lock_cpu_hotplug from kernel/sched.c.\n\n[PATCH 4/4] :\tIn workqueue_cpu_callback function, acquire(release) the\n\t\tworkqueue_mutex while handling\n\t\tCPU_LOCK_ACQUIRE(CPU_LOCK_RELEASE).\n\nIf the per-subsystem-locking approach survives the test of time, we can expect\na slow phasing out of lock_cpu_hotplug, which has not yet been eliminated in\nthese patches :)\n\nThis patch:\n\nProvide notifier_call_chain with an option to call only a specified number of\nnotifiers and also record the number of call to notifiers made.\n\nThe need for this enhancement was identified in the post entitled\n\"Slab - Eliminate lock_cpu_hotplug from slab\"\n(http://lkml.org/lkml/2006/10/28/92) by Ravikiran G Thirumalai and\nAndrew Morton.\n\nThis patch adds two additional parameters to notifier_call_chain API namely\n - int nr_to_calls : Number of notifier_functions to be called.\n \t\t The don\u0027t care value is -1.\n\n - unsigned int *nr_calls : Records the total number of notifier_funtions\n\t\t\t called by notifier_call_chain. The don\u0027t care\n\t\t\t value is NULL.\n\n[michal.k.k.piotrowski@gmail.com: build fix]\nCredit: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Gautham R Shenoy \u003cego@in.ibm.com\u003e\nSigned-off-by: Michal Piotrowski \u003cmichal.k.k.piotrowski@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "eabc069401bcf45bcc3f19e643017bf761780aa8", "tree": "1175b8bed2d88cc9f437edbc239d7681f13b8a7d", "parents": [ "b2896d2e75c87ea6a842c088db730b03c91db737" ], "author": { "name": "Alan Stern", "email": "stern@rowland.harvard.edu", "time": "Wed Oct 04 02:17:04 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Wed Oct 04 07:55:30 2006 -0700" }, "message": "[PATCH] Add SRCU-based notifier chains\n\nThis patch (as751) adds a new type of notifier chain, based on the SRCU\n(Sleepable Read-Copy Update) primitives recently added to the kernel. An\nSRCU notifier chain is much like a blocking notifier chain, in that it must\nbe called in process context and its callout routines are allowed to sleep.\n The difference is that the chain\u0027s links are protected by the SRCU\nmechanism rather than by an rw-semaphore, so calling the chain has\nextremely low overhead: no memory barriers and no cache-line bouncing. On\nthe other hand, unregistering from the chain is expensive and the chain\nhead requires special runtime initialization (plus cleanup if it is to be\ndeallocated).\n\nSRCU notifiers are appropriate for notifiers that will be called very\nfrequently and for which unregistration occurs very seldom. The proposed\n\"task notifier\" scheme qualifies, as may some of the network notifiers.\n\nSigned-off-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nAcked-by: Paul E. McKenney \u003cpaulmck@us.ibm.com\u003e\nAcked-by: Chandra Seetharaman \u003csekharan@us.ibm.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "e4d919188554a77c798a267e098059bc9aa39726", "tree": "bb5e47e09f5d107db44358ad668988f5ae768ade", "parents": [ "9cebb5526833059f327d237a032422c762378b2a" ], "author": { "name": "Ingo Molnar", "email": "mingo@elte.hu", "time": "Mon Jul 03 00:24:34 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jul 03 15:27:02 2006 -0700" }, "message": "[PATCH] lockdep: locking init debugging improvement\n\nLocking init improvement:\n\n - introduce and use __SPIN_LOCK_UNLOCKED for array initializations,\n to pass in the name string of locks, used by debugging\n\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\nSigned-off-by: Arjan van de Ven \u003carjan@linux.intel.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "e041c683412d5bf44dc2b109053e3b837b71742d", "tree": "9d271066ef379da0c0fb3b8cb4137abd5d2ebba0", "parents": [ "76b81e2b0e2241accebcc68e126bc5ab958661b9" ], "author": { "name": "Alan Stern", "email": "stern@rowland.harvard.edu", "time": "Mon Mar 27 01:16:30 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Mar 27 08:44:50 2006 -0800" }, "message": "[PATCH] Notifier chain update: API changes\n\nThe kernel\u0027s implementation of notifier chains is unsafe. There is no\nprotection against entries being added to or removed from a chain while the\nchain is in use. The issues were discussed in this thread:\n\n http://marc.theaimsgroup.com/?l\u003dlinux-kernel\u0026m\u003d113018709002036\u0026w\u003d2\n\nWe noticed that notifier chains in the kernel fall into two basic usage\nclasses:\n\n\t\"Blocking\" chains are always called from a process context\n\tand the callout routines are allowed to sleep;\n\n\t\"Atomic\" chains can be called from an atomic context and\n\tthe callout routines are not allowed to sleep.\n\nWe decided to codify this distinction and make it part of the API. Therefore\nthis set of patches introduces three new, parallel APIs: one for blocking\nnotifiers, one for atomic notifiers, and one for \"raw\" notifiers (which is\nreally just the old API under a new name). New kinds of data structures are\nused for the heads of the chains, and new routines are defined for\nregistration, unregistration, and calling a chain. The three APIs are\nexplained in include/linux/notifier.h and their implementation is in\nkernel/sys.c.\n\nWith atomic and blocking chains, the implementation guarantees that the chain\nlinks will not be corrupted and that chain callers will not get messed up by\nentries being added or removed. For raw chains the implementation provides no\nguarantees at all; users of this API must provide their own protections. (The\nidea was that situations may come up where the assumptions of the atomic and\nblocking APIs are not appropriate, so it should be possible for users to\nhandle these things in their own way.)\n\nThere are some limitations, which should not be too hard to live with. For\natomic/blocking chains, registration and unregistration must always be done in\na process context since the chain is protected by a mutex/rwsem. Also, a\ncallout routine for a non-raw chain must not try to register or unregister\nentries on its own chain. (This did happen in a couple of places and the code\nhad to be changed to avoid it.)\n\nSince atomic chains may be called from within an NMI handler, they cannot use\nspinlocks for synchronization. Instead we use RCU. The overhead falls almost\nentirely in the unregister routine, which is okay since unregistration is much\nless frequent that calling a chain.\n\nHere is the list of chains that we adjusted and their classifications. None\nof them use the raw API, so for the moment it is only a placeholder.\n\n ATOMIC CHAINS\n -------------\narch/i386/kernel/traps.c:\t\ti386die_chain\narch/ia64/kernel/traps.c:\t\tia64die_chain\narch/powerpc/kernel/traps.c:\t\tpowerpc_die_chain\narch/sparc64/kernel/traps.c:\t\tsparc64die_chain\narch/x86_64/kernel/traps.c:\t\tdie_chain\ndrivers/char/ipmi/ipmi_si_intf.c:\txaction_notifier_list\nkernel/panic.c:\t\t\t\tpanic_notifier_list\nkernel/profile.c:\t\t\ttask_free_notifier\nnet/bluetooth/hci_core.c:\t\thci_notifier\nnet/ipv4/netfilter/ip_conntrack_core.c:\tip_conntrack_chain\nnet/ipv4/netfilter/ip_conntrack_core.c:\tip_conntrack_expect_chain\nnet/ipv6/addrconf.c:\t\t\tinet6addr_chain\nnet/netfilter/nf_conntrack_core.c:\tnf_conntrack_chain\nnet/netfilter/nf_conntrack_core.c:\tnf_conntrack_expect_chain\nnet/netlink/af_netlink.c:\t\tnetlink_chain\n\n BLOCKING CHAINS\n ---------------\narch/powerpc/platforms/pseries/reconfig.c:\tpSeries_reconfig_chain\narch/s390/kernel/process.c:\t\tidle_chain\narch/x86_64/kernel/process.c\t\tidle_notifier\ndrivers/base/memory.c:\t\t\tmemory_chain\ndrivers/cpufreq/cpufreq.c\t\tcpufreq_policy_notifier_list\ndrivers/cpufreq/cpufreq.c\t\tcpufreq_transition_notifier_list\ndrivers/macintosh/adb.c:\t\tadb_client_list\ndrivers/macintosh/via-pmu.c\t\tsleep_notifier_list\ndrivers/macintosh/via-pmu68k.c\t\tsleep_notifier_list\ndrivers/macintosh/windfarm_core.c\twf_client_list\ndrivers/usb/core/notify.c\t\tusb_notifier_list\ndrivers/video/fbmem.c\t\t\tfb_notifier_list\nkernel/cpu.c\t\t\t\tcpu_chain\nkernel/module.c\t\t\t\tmodule_notify_list\nkernel/profile.c\t\t\tmunmap_notifier\nkernel/profile.c\t\t\ttask_exit_notifier\nkernel/sys.c\t\t\t\treboot_notifier_list\nnet/core/dev.c\t\t\t\tnetdev_chain\nnet/decnet/dn_dev.c:\t\t\tdnaddr_chain\nnet/ipv4/devinet.c:\t\t\tinetaddr_chain\n\nIt\u0027s possible that some of these classifications are wrong. If they are,\nplease let us know or submit a patch to fix them. Note that any chain that\ngets called very frequently should be atomic, because the rwsem read-locking\nused for blocking chains is very likely to incur cache misses on SMP systems.\n(However, if the chain\u0027s callout routines may sleep then the chain cannot be\natomic.)\n\nThe patch set was written by Alan Stern and Chandra Seetharaman, incorporating\nmaterial written by Keith Owens and suggestions from Paul McKenney and Andrew\nMorton.\n\n[jes@sgi.com: restructure the notifier chain initialization macros]\nSigned-off-by: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: Chandra Seetharaman \u003csekharan@us.ibm.com\u003e\nSigned-off-by: Jes Sorensen \u003cjes@sgi.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "d8a33ac435c43a1a404b2ec560ef1d1536710c36", "tree": "04359c09e0731e9c33a8c2dd80cc69404e0dde60", "parents": [ "45b30105e7231b70bb855923dbca443ee3ba44c3" ], "author": { "name": "Stephen Hemminger", "email": "shemminger@osdl.org", "time": "Sun May 29 14:13:47 2005 -0700" }, "committer": { "name": "David S. Miller", "email": "davem@davemloft.net", "time": "Sun May 29 14:13:47 2005 -0700" }, "message": "[BRIDGE]: features change notification\n\nResend of earlier patch (no changes) from Catalin used to provide\ndevice feature change notification.\n\nSigned-off-by: Catalin BOIE \u003ccatab at umbrella.ro\u003e\nAcked-by: Stephen Hemminger \u003cshemminger@osdl.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n" }, { "commit": "1da177e4c3f41524e886b7f1b8a0c1fc7321cac2", "tree": "0bba044c4ce775e45a88a51686b5d9f90697ea9d", "parents": [], "author": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@ppc970.osdl.org", "time": "Sat Apr 16 15:20:36 2005 -0700" }, "message": "Linux-2.6.12-rc2\n\nInitial git repository build. I\u0027m not bothering with the full history,\neven though we have it. We can create a separate \"historical\" git\narchive of that later if we want to, and in the meantime it\u0027s about\n3.2GB when imported into git - space that would just make the early\ngit days unnecessarily complicated, when we don\u0027t have a lot of good\ninfrastructure for it.\n\nLet it rip!\n" } ] }