1. 01 Jul, 2006 1 commit
  2. 30 Jun, 2006 3 commits
  3. 29 Jun, 2006 12 commits
  4. 28 Jun, 2006 2 commits
    • Chandra Seetharaman's avatar
      [PATCH] cpu hotplug: revert initdata patch submitted for 2.6.17 · 054cc8a2
      Chandra Seetharaman authored
      This patch reverts notifier_block changes made in 2.6.17
      Signed-off-by: default avatarChandra Seetharaman <sekharan@us.ibm.com>
      Cc: Ashok Raj <ashok.raj@intel.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • KAMEZAWA Hiroyuki's avatar
      [PATCH] node hotplug: register cpu: remove node struct · 76b67ed9
      KAMEZAWA Hiroyuki authored
      With Goto-san's patch, we can add new pgdat/node at runtime.  I'm now
      considering node-hot-add with cpu + memory on ACPI.
      I found acpi container, which describes node, could evaluate cpu before
      memory. This means cpu-hot-add occurs before memory hot add.
      In most part, cpu-hot-add doesn't depend on node hot add.  But register_cpu(),
      which creates symbolic link from node to cpu, requires that node should be
      onlined before register_cpu().  When a node is onlined, its pgdat should be
      This patch-set holds off creating symbolic link from node to cpu
      until node is onlined.
      This removes node arguments from register_cpu().
      Now, register_cpu() requires 'struct node' as its argument.  But the array of
      struct node is now unified in driver/base/node.c now (By Goto's node hotplug
      patch).  We can get struct node in generic way.  So, this argument is not
      necessary now.
      This patch also guarantees add cpu under node only when node is onlined.  It
      is necessary for node-hot-add vs.  cpu-hot-add patch following this.
      Moreover, register_cpu calculates cpu->node_id by cpu_to_node() without regard
      to its 'struct node *root' argument.  This patch removes it.
      Also modify callers of register_cpu()/unregister_cpu, whose args are changed
      by register-cpu-remove-node-struct patch.
      [Brice.Goglin@ens-lyon.org: fix it]
      Signed-off-by: default avatarKAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
      Cc: Yasunori Goto <y-goto@jp.fujitsu.com>
      Cc: Ashok Raj <ashok.raj@intel.com>
      Cc: Dave Hansen <haveblue@us.ibm.com>
      Signed-off-by: default avatarBrice Goglin <Brice.Goglin@ens-lyon.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  5. 26 Jun, 2006 4 commits
  6. 25 Jun, 2006 1 commit
  7. 23 Jun, 2006 2 commits
    • Andrew Morton's avatar
      [PATCH] s390_hypfs filesystem: get_sb_single() fix · a5cf4b9a
      Andrew Morton authored
      Update hypfs for dhowells API changes.
      Cc: Pekka Enberg <penberg@cs.helsinki.fi>
      Cc: Ingo Oeser <ioe-lkml@rameria.de>
      Cc: Joern Engel <joern@wohnheim.fh-wedel.de>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Michael Holzheu <holzheu@de.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
    • Michael Holzheu's avatar
      [PATCH] s390_hypfs filesystem · 24bbb1fa
      Michael Holzheu authored
      On zSeries machines there exists an interface which allows the operating
      system to retrieve LPAR hypervisor accounting data.  For example, it is
      possible to get usage data for physical and virtual cpus.  In order to
      provide this information to user space programs, I implemented a new
      virtual Linux file system named 's390_hypfs' using the Linux 2.6 libfs
      framework.  The name 's390_hypfs' stands for 'S390 Hypervisor Filesystem'.
      All the accounting information is put into different virtual files which
      can be accessed from user space.  All data is represented as ASCII strings.
      When the file system is mounted the accounting information is retrieved and
      a file system tree is created with the attribute files containing the cpu
      information.  The content of the files remains unchanged until a new update
      is made.  An update can be triggered from user space through writing
      'something' into a special purpose update file.
      We create the following directory structure:
      - update: File to trigger update
      - cpus/: Directory for all physical cpus
      - cpus/<cpu-id>/: Directory for one physical cpu.
      - cpus/<cpu-id>/type: Type name of physical zSeries cpu.
      - cpus/<cpu-id>/mgmtime: Physical-LPAR-management time in microseconds.
      - hyp/: Directory for hypervisor information
      - hyp/type: Typ of hypervisor (currently only 'LPAR Hypervisor')
      - systems/: Directory for all LPARs
      - systems/<lpar-name>/: Directory for one LPAR.
      - systems/<lpar-name>/cpus/<cpu-id>/: Directory for the virtual cpus
      - systems/<lpar-name>/cpus/<cpu-id>/type: Typ of cpu.
      - systems/<lpar-name>/cpus/<cpu-id>/mgmtime:
      Accumulated number of microseconds during which a physical
      CPU was assigned to the logical cpu and the cpu time was
      consumed by the hypervisor and was not provided to
      the LPAR (LPAR overhead).
      - systems/<lpar-name>/cpus/<cpu-id>/cputime:
      Accumulated number of microseconds during which a physical CPU
      was assigned to the logical cpu and the cpu time was consumed
      by the LPAR.
      - systems/<lpar-name>/cpus/<cpu-id>/onlinetime:
      Accumulated number of microseconds during which the logical CPU
      has been online.
      As mount point for the filesystem /sys/hypervisor/s390 is created.
      The update process is triggered when writing 'something' into the
      'update' file at the top level hypfs directory. You can do this e.g.
      with 'echo 1 > update'. During the update the whole directory structure
      is deleted and built up again.
      Cc: Pekka Enberg <penberg@cs.helsinki.fi>
      Cc: Ingo Oeser <ioe-lkml@rameria.de>
      Cc: Joern Engel <joern@wohnheim.fh-wedel.de>
      Acked-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: default avatarMichael Holzheu <holzheu@de.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  8. 25 May, 2006 1 commit
  9. 21 May, 2006 1 commit
  10. 15 May, 2006 2 commits
  11. 02 May, 2006 1 commit
  12. 01 May, 2006 1 commit
  13. 28 Apr, 2006 4 commits
  14. 26 Apr, 2006 1 commit
  15. 11 Apr, 2006 2 commits
  16. 31 Mar, 2006 1 commit
  17. 27 Mar, 2006 1 commit
    • Alan Stern's avatar
      [PATCH] Notifier chain update: API changes · e041c683
      Alan Stern authored
      The kernel's implementation of notifier chains is unsafe.  There is no
      protection against entries being added to or removed from a chain while the
      chain is in use.  The issues were discussed in this thread:
      We noticed that notifier chains in the kernel fall into two basic usage
      	"Blocking" chains are always called from a process context
      	and the callout routines are allowed to sleep;
      	"Atomic" chains can be called from an atomic context and
      	the callout routines are not allowed to sleep.
      We decided to codify this distinction and make it part of the API.  Therefore
      this set of patches introduces three new, parallel APIs: one for blocking
      notifiers, one for atomic notifiers, and one for "raw" notifiers (which is
      really just the old API under a new name).  New kinds of data structures are
      used for the heads of the chains, and new routines are defined for
      registration, unregistration, and calling a chain.  The three APIs are
      explained in include/linux/notifier.h and their implementation is in
      With atomic and blocking chains, the implementation guarantees that the chain
      links will not be corrupted and that chain callers will not get messed up by
      entries being added or removed.  For raw chains the implementation provides no
      guarantees at all; users of this API must provide their own protections.  (The
      idea was that situations may come up where the assumptions of the atomic and
      blocking APIs are not appropriate, so it should be possible for users to
      handle these things in their own way.)
      There are some limitations, which should not be too hard to live with.  For
      atomic/blocking chains, registration and unregistration must always be done in
      a process context since the chain is protected by a mutex/rwsem.  Also, a
      callout routine for a non-raw chain must not try to register or unregister
      entries on its own chain.  (This did happen in a couple of places and the code
      had to be changed to avoid it.)
      Since atomic chains may be called from within an NMI handler, they cannot use
      spinlocks for synchronization.  Instead we use RCU.  The overhead falls almost
      entirely in the unregister routine, which is okay since unregistration is much
      less frequent that calling a chain.
      Here is the list of chains that we adjusted and their classifications.  None
      of them use the raw API, so for the moment it is only a placeholder.
      arch/i386/kernel/traps.c:		i386die_chain
      arch/ia64/kernel/traps.c:		ia64die_chain
      arch/powerpc/kernel/traps.c:		powerpc_die_chain
      arch/sparc64/kernel/traps.c:		sparc64die_chain
      arch/x86_64/kernel/traps.c:		die_chain
      drivers/char/ipmi/ipmi_si_intf.c:	xaction_notifier_list
      kernel/panic.c:				panic_notifier_list
      kernel/profile.c:			task_free_notifier
      net/bluetooth/hci_core.c:		hci_notifier
      net/ipv4/netfilter/ip_conntrack_core.c:	ip_conntrack_chain
      net/ipv4/netfilter/ip_conntrack_core.c:	ip_conntrack_expect_chain
      net/ipv6/addrconf.c:			inet6addr_chain
      net/netfilter/nf_conntrack_core.c:	nf_conntrack_chain
      net/netfilter/nf_conntrack_core.c:	nf_conntrack_expect_chain
      net/netlink/af_netlink.c:		netlink_chain
      arch/powerpc/platforms/pseries/reconfig.c:	pSeries_reconfig_chain
      arch/s390/kernel/process.c:		idle_chain
      arch/x86_64/kernel/process.c		idle_notifier
      drivers/base/memory.c:			memory_chain
      drivers/cpufreq/cpufreq.c		cpufreq_policy_notifier_list
      drivers/cpufreq/cpufreq.c		cpufreq_transition_notifier_list
      drivers/macintosh/adb.c:		adb_client_list
      drivers/macintosh/via-pmu.c		sleep_notifier_list
      drivers/macintosh/via-pmu68k.c		sleep_notifier_list
      drivers/macintosh/windfarm_core.c	wf_client_list
      drivers/usb/core/notify.c		usb_notifier_list
      drivers/video/fbmem.c			fb_notifier_list
      kernel/cpu.c				cpu_chain
      kernel/module.c				module_notify_list
      kernel/profile.c			munmap_notifier
      kernel/profile.c			task_exit_notifier
      kernel/sys.c				reboot_notifier_list
      net/core/dev.c				netdev_chain
      net/decnet/dn_dev.c:			dnaddr_chain
      net/ipv4/devinet.c:			inetaddr_chain
      It's possible that some of these classifications are wrong.  If they are,
      please let us know or submit a patch to fix them.  Note that any chain that
      gets called very frequently should be atomic, because the rwsem read-locking
      used for blocking chains is very likely to incur cache misses on SMP systems.
      (However, if the chain's callout routines may sleep then the chain cannot be
      The patch set was written by Alan Stern and Chandra Seetharaman, incorporating
      material written by Keith Owens and suggestions from Paul McKenney and Andrew
      [jes@sgi.com: restructure the notifier chain initialization macros]
      Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: default avatarChandra Seetharaman <sekharan@us.ibm.com>
      Signed-off-by: default avatarJes Sorensen <jes@sgi.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>