1. 26 3月, 2006 3 次提交
    • A
      [PATCH] x86: make CONFIG_HOTPLUG_CPU depend on !X86_PC · d3f4aaa3
      Ashok Raj 提交于
      Make CONFIG_HOTPLUG_CPU depend on !X86_PC, so we need to turn on either
      CONFIG_GENERICARCH, CONFIG_BIGSMP or any other subarch except X86_PC when
      CONFIG_HOTPLUG_CPU=y
      
      With 2.6.15+ kernels when CONFIG_HOTPLUG_CPU is turned on we switch to
      bigsmp mode for sending IPI's and ioapic configurations that caused the
      following error message.
      
      >> More than 8 CPUs detected and CONFIG_X86_PC cannot handle it.
      >> Use CONFIG_X86_GENERICARCH or CONFIG_X86_BIGSMP.
      
      Originally bigsmp was added just to handle >8 cpus, but now with hotplug
      cpu support we need to use bigsmp mode (why?  see below), that cause the
      above error message even if there were less than 8 cpus in the system.
      
      The message is bogus, but we are cannot use logical flat mode due to issues
      with broadcast IPI can confuse a CPU just comming up.  We use flat physical
      mode just like x86_64 case.  More details on why bigsmp now uses flat
      physical mode (vs.  cluster mode) in following link.
      
      http://marc.theaimsgroup.com/?l=linux-kernel&m=113261865814107&w=2Signed-off-by: NAshok Raj <ashok.raj@intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      d3f4aaa3
    • T
      [PATCH] sys_alarm() unsigned signed conversion fixup · c08b8a49
      Thomas Gleixner 提交于
      alarm() calls the kernel with an unsigend int timeout in seconds.  The
      value is stored in the tv_sec field of a struct timeval to setup the
      itimer.  The tv_sec field of struct timeval is of type long, which causes
      the tv_sec value to be negative on 32 bit machines if seconds > INT_MAX.
      
      Before the hrtimer merge (pre 2.6.16) such a negative value was converted
      to the maximum jiffies timeout by the timeval_to_jiffies conversion.  It's
      not clear whether this was intended or just happened to be done by the
      timeval_to_jiffies code.
      
      hrtimers expect a timeval in canonical form and treat a negative timeout as
      already expired.  This breaks the legitimate usage of alarm() with a
      timeout value > INT_MAX seconds.
      
      For 32 bit machines it is therefor necessary to limit the internal seconds
      value to avoid API breakage.  Instead of doing this in all implementations
      of sys_alarm the duplicated sys_alarm code is moved into a common function
      in itimer.c
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      c08b8a49
    • A
      [PATCH] fix DMI onboard device discovery · bc83455b
      Andrey Panin 提交于
      Attached patch fixes invalid pointer arithmetic in DMI code to make onboard
      device discovery working again.
      
      akpm: bug has been present since dmi_find_device() was added in 2.6.14.
      Affects ipmi only (I think) - the symptoms weren't described.
      
      akpm: changed to use pointer arithmetic rather than open-coded sizeof.
      Signed-off-by: NAndrey Panin <pazke@donpac.ru>
      Cc: Corey Minyard <minyard@acm.org>
      Cc: <stable@kernel.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      bc83455b
  2. 24 3月, 2006 14 次提交
  3. 23 3月, 2006 23 次提交
反馈
建议
客服 返回
顶部