1. 23 Jan, 2007 5 commits
    • Venkatesh Pallipadi's avatar
      [PATCH] Revert nmi_known_cpu() check during boot option parsing · 58d9ce7d
      Venkatesh Pallipadi authored
      Commit f2802e7f and its x86 version
      (b7471c6d) adds nmi_known_cpu() check
      while parsing boot options in x86_64 and i386.
      
      With that, "nmi_watchdog=2" stops working for me on Intel Core 2 CPU
      based system.
      
      The problem is, setup_nmi_watchdog is called while parsing the boot
      option and identify_cpu is not done yet.  So, the return value of
      nmi_known_cpu() is not valid at this point.
      
      So revert that check.  This should not have any adverse effect as the
      nmi_known_cpu() check is done again later in enable_lapic_nmi_watchdog().
      Signed-off-by: default avatarVenkatesh Pallipadi <venkatesh.pallipadi@intel.com>
      Cc: Don Zickus <dzickus@redhat.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Ingo Molnar <mingo@elte.hu>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      58d9ce7d
    • Andrew Morton's avatar
      [PATCH] fix "kvm: add vm exit profiling" · bbe1a59b
      Andrew Morton authored
      export profile_hits() on !SMP too.
      
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Avi Kivity <avi@qumranet.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      bbe1a59b
    • James Bottomley's avatar
      [PATCH] x86: fix PDA variables to work during boot · 9ee79a3d
      James Bottomley authored
      The current PDA code, which went in in post 2.6.19 has a flaw in that it
      doesn't correctly cycle the GDT and %GS segment through the boot PDA,
      the CPU PDA and finally the per-cpu PDA.
      
      The bug generally doesn't show up if the boot CPU id is zero, but
      everything falls apart for a non zero boot CPU id.  The basically kills
      voyager which is perfectly capable of doing non zero CPU id boots, so
      voyager currently won't boot without this.
      
      The fix is to be careful and actually do the GDT setups correctly.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
      Cc: Andi Kleen <ak@suse.de>
      Cc: Jeremy Fitzhardinge <jeremy@goop.org>
      Cc: Andrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      9ee79a3d
    • Linus Torvalds's avatar
      Merge git://git.infradead.org/mtd-2.6 · ebcccd14
      Linus Torvalds authored
      * git://git.infradead.org/mtd-2.6: (84 commits)
        [JFFS2] debug.h: include <linux/sched.h> for current->pid
        [MTD] OneNAND: Handle DDP chip boundary during read-while-load
        [MTD] OneNAND: return ecc error code only when 2-bit ecc occurs
        [MTD] OneNAND: Implement read-while-load
        [MTD] OneNAND: fix onenand_wait bug in read ecc error
        [MTD] OneNAND: release CPU in cycles
        [MTD] OneNAND: add subpage write support
        [MTD] OneNAND: fix onenand_wait bug
        [JFFS2] use the ref_offset macro
        [JFFS2] Reschedule in loops
        [JFFS2] Fix error-path leak in summary scan
        [JFFS2] add cond_resched() when garbage collecting deletion dirent
        [MTD] Nuke IVR leftovers
        [MTD] OneNAND: fix oob handling in recent oob patch
        [MTD] Fix ssfdc blksize typo
        [JFFS2] replace kmalloc+memset with kzalloc
        [MTD] Fix SSFDC build for variable blocksize.
        [MTD] ESB2ROM uses PCI
        [MTD] of_device-based physmap driver
        [MTD] Support combined RedBoot FIS directory and configuration area
        ...
      ebcccd14
    • Herbert Xu's avatar
      [PATCH] vmx: Fix register constraint in launch code · e0015489
      Herbert Xu authored
      Both "=r" and "=g" breaks my build on i386:
      
        $ make
          CC [M]  drivers/kvm/vmx.o
        {standard input}: Assembler messages:
        {standard input}:3318: Error: bad register name `%sil'
        make[1]: *** [drivers/kvm/vmx.o] Error 1
        make: *** [_module_drivers/kvm] Error 2
      
      The reason is that setbe requires an 8-bit register but "=r" does not
      constrain the target register to be one that has an 8-bit version on
      i386.
      
      According to
      
      	http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10153
      
      the correct constraint is "=q".
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      e0015489
  2. 22 Jan, 2007 35 commits