1. 30 6月, 2006 25 次提交
  2. 29 6月, 2006 1 次提交
  3. 28 6月, 2006 12 次提交
    • B
      f831335d
    • A
      ACPI: restore comment justifying 'extra' P_LVLx access · b488f021
      Andreas Mohr 提交于
      While trying to look for superfluous I/O accesses that can be optimized
      away, I stumbled upon this ACPI sleep I/O access and couldn't figure out
      why the hell this dummy op was necessary.
      After more than one hour of internet research, I had collected a sufficient
      number of documents (among those very old kernel versions) that finally
      told me what this dummy read was about: STPCLK# doesn't get asserted in time
      on (some) chipsets, which is why we need to have a dummy I/O read to delay
      further instruction processing until the CPU is fully stopped.
      Signed-off-by: NAndreas Mohr <andi@lisas.de>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      b488f021
    • D
      ACPI: C-States: only demote on current bus mastering activity · c4a001b1
      Dominik Brodowski 提交于
      Only if bus master activity is going on at the present, we should avoid
      entering C3-type sleep, as it might be a faulty transition.  As long as the
      bm_activity bitmask was based on the number of calls to the ACPI idle
      function, looking at previous moments made sense.  Now, with it being based on
      what happened this jiffy, looking at this jiffy should be sufficient.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      c4a001b1
    • D
      ACPI: C-States: bm_activity improvements · c5ab81ca
      Dominik Brodowski 提交于
      Do not assume there was bus mastering activity if the idle handler didn't get
      called, as there's only reason to not enter C3-type sleep if there is bus
      master activity going on.  Only for the "promotion" into C3-type sleep bus
      mastering activity is taken into account, and there only current bus mastering
      activity, and not pure guessing should lead to the decision on whether to
      enter C3-type sleep or not.
      
      Also, as bm_activity is a jiffy-based bitmask (bit 0: bus mastering activity
      during this juffy, bit 31: bus mastering activity 31 jiffies ago), fix the
      setting of bit 0, as it might be called multiple times within one jiffy.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      c5ab81ca
    • D
      ACPI: C-States: accounting of sleep states · a3c6598f
      Dominik Brodowski 提交于
      Track the actual time spent in C-States (C2 upwards, we can't determine this
      for C1), not only the number of invocations.  This is especially useful for
      dynamic ticks / "tickless systems", but is also of interest on normal systems,
      as any interrupt activity leads to C-States being exited, not only the timer
      interrupt.
      
      The time is being measured in PM timer ticks, so an increase by one equals 279
      nanoseconds.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      a3c6598f
    • B
      ACPI: ACPICA 20060623 · 967440e3
      Bob Moore 提交于
      Implemented a new acpi_spinlock type for the OSL lock
      interfaces.  This allows the type to be customized to
      the host OS for improved efficiency (since a spinlock is
      usually a very small object.)
      
      Implemented support for "ignored" bits in the ACPI
      registers.  According to the ACPI specification, these
      bits should be preserved when writing the registers via
      a read/modify/write cycle. There are 3 bits preserved
      in this manner: PM1_CONTROL[0] (SCI_EN), PM1_CONTROL[9],
      and PM1_STATUS[11].
      http://bugzilla.kernel.org/show_bug.cgi?id=3691
      
      Implemented the initial deployment of new OSL mutex
      interfaces.  Since some host operating systems have
      separate mutex and semaphore objects, this feature was
      requested. The base code now uses mutexes (and the new
      mutex interfaces) wherever a binary semaphore was used
      previously. However, for the current release, the mutex
      interfaces are defined as macros to map them to the
      existing semaphore interfaces.
      
      Fixed several problems with the support for the control
      method SyncLevel parameter. The SyncLevel now works
      according to the ACPI specification and in concert with the
      Mutex SyncLevel parameter, since the current SyncLevel is
      a property of the executing thread. Mutual exclusion for
      control methods is now implemented with a mutex instead
      of a semaphore.
      
      Fixed three instances of the use of the C shift operator
      in the bitfield support code (exfldio.c) to avoid the use
      of a shift value larger than the target data width. The
      behavior of C compilers is undefined in this case and can
      cause unpredictable results, and therefore the case must
      be detected and avoided.  (Fiodor Suietov)
      
      Added an info message whenever an SSDT or OEM table
      is loaded dynamically via the Load() or LoadTable()
      ASL operators. This should improve debugging capability
      since it will show exactly what tables have been loaded
      (beyond the tables present in the RSDT/XSDT.)
      Signed-off-by: NBob Moore <robert.moore@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      967440e3
    • K
      ACPI: dock driver · a5e1b940
      Kristen Accardi 提交于
      Create a driver which lives in the acpi subsystem to handle dock events.
      This driver is not an "ACPI" driver, because acpi drivers require that the
      object be present when the driver is loaded.
      Signed-off-by: NKristen Carlson Accardi <kristen.c.accardi@intel.com>
      Cc: Dave Hansen <haveblue@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      a5e1b940
    • Y
      [PATCH] pgdat allocation for new node add (get node id by acpi) · 1e3590e2
      Yasunori Goto 提交于
      This is to find node id from acpi's handle of memory_device in DSDT.  _PXM for
      the new node can be found by acpi_get_pxm() by using new memory's handle.  So,
      node id can be found by pxm_to_nid_map[].
      
        This patch becomes simpler than v2 of node hot-add patch.
        Because old add_memory() function doesn't have node id parameter.
        So, kernel must find its handle by physical address via DSDT again.
        But, v3 just give node id to add_memory() now.
      Signed-off-by: NYasunori Goto <y-goto@jp.fujitsu.com>
      Cc: Dave Hansen <haveblue@us.ibm.com>
      Cc: "Brown, Len" <len.brown@intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      1e3590e2
    • Y
      [PATCH] pgdat allocation for new node add (specify node id) · bc02af93
      Yasunori Goto 提交于
      Change the name of old add_memory() to arch_add_memory.  And use node id to
      get pgdat for the node at NODE_DATA().
      
      Note: Powerpc's old add_memory() is defined as __devinit. However,
            add_memory() is usually called only after bootup.
            I suppose it may be redundant. But, I'm not well known about powerpc.
            So, I keep it. (But, __meminit is better at least.)
      Signed-off-by: NYasunori Goto <y-goto@jp.fujitsu.com>
      Cc: Dave Hansen <haveblue@us.ibm.com>
      Cc: "Brown, Len" <len.brown@intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      bc02af93
    • Y
      [PATCH] Catch notification of memory add event of ACPI via container driver.... · dd56a8e3
      Yasunori Goto 提交于
      [PATCH] Catch notification of memory add event of ACPI via container driver. (avoid redundant call add_memory)
      
      When acpi_memory_device_init() is called at boottime to register struct
      memory acpi_memory_device, acpi_bus_add() are called via
      acpi_driver_attach().
      
      But it also calls ops->start() function.  It is called even if the memory
      blocks are initialized at early boottime.  In this case add_memory() return
      -EEXIST, and the memory blocks becomes INVALID state even if it is normal.
      
      This is patch to avoid calling add_memory() for already available memory.
      
      [akpm@osdl.org: coding cleanups]
      Signed-off-by: NYasunori Goto <y-goto@jp.fujitsu.com>
      Cc: "Brown, Len" <len.brown@intel.com>
      Cc: Dave Hansen <haveblue@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      dd56a8e3
    • Y
      [PATCH] Catch notification of memory add event of ACPI via container driver.... · 1f425994
      Yasunori Goto 提交于
      [PATCH] Catch notification of memory add event of ACPI via container driver. (register start func for memory device)
      
      This is a patch to call add_memroy() when notify reaches for new node's add
      event.
      
      When new node is added, notify of ACPI reaches container device which means
      the node.
      
      Container device driver calls acpi_bus_scan() to find and add belonging
      devices (which means cpu, memory and so on).  Its function calls add and
      start function of belonging devices's driver.
      
      Howevever, current memory hotplug driver just register add function to
      create sysfs file for its memory.  But, acpi_memory_enable_device() is not
      called because it is considered just the case that notify reaches memory
      device directly.  So, if notify reaches container device nothing can call
      add_memory().
      
      This is a patch to create start function which calls add_memory().
      add_memory() can be called by this when notify reaches container device.
      
      [akpm@osdl.org: coding cleanups]
      Signed-off-by: NYasunori Goto <y-goto@jp.fujitsu.com>
      Cc: "Brown, Len" <len.brown@intel.com>
      Cc: Dave Hansen <haveblue@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      1f425994
    • K
      [PATCH] acpi memory hotplug cannot manage _CRS with plural resoureces · 9ac02398
      KAMEZAWA Hiroyuki 提交于
      Current acpi memory hotplug just looks into the first entry of resources in
      _CRS.  But, _CRS can contain plural resources.  So, if _CRS contains plural
      resoureces, acpi memory hot add cannot add all memory.
      
      With this patch, acpi memory hotplug can deal with Memory Device, whose
      _CRS contains plural resources.
      
      Tested on ia64 memory hotplug test envrionment (not emulation, uses alpha
      version firmware which supports dynamic reconfiguration of NUMA.)
      
      Note: Microsoft's Windows Server 2003 requires big (>4G)resoureces to be
            divided into small (<4G) resources. looks crazy, but not invalid.
            (See http://www.microsoft.com/whdc/system/pnppwr/hotadd/hotaddmem.mspx)
            For this reason, a firmware vendor who supports Windows writes plural
            resources in a _CRS even if they are contiguous.
      Signed-off-by: NKenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
      Signed-off-by: NKAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
      Cc: "Brown, Len" <len.brown@intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      9ac02398
  4. 27 6月, 2006 2 次提交