1. 21 Nov, 2012 5 commits
  2. 20 Nov, 2012 13 commits
  3. 13 Nov, 2012 2 commits
  4. 11 Nov, 2012 2 commits
    • Geert Uytterhoeven's avatar
      mfd: Remove Unicode Byte Order Marks from da9055 · 90a38d99
      Geert Uytterhoeven authored
      
      Older gcc (< 4.4) doesn't like files starting with Unicode BOMs:
      
      include/linux/mfd/da9055/core.h:1: error: stray ‘\357’ in program
      include/linux/mfd/da9055/core.h:1: error: stray ‘\273’ in program
      include/linux/mfd/da9055/core.h:1: error: stray ‘\277’ in program
      include/linux/mfd/da9055/pdata.h:1: error: stray ‘\357’ in program
      include/linux/mfd/da9055/pdata.h:1: error: stray ‘\273’ in program
      include/linux/mfd/da9055/pdata.h:1: error: stray ‘\277’ in program
      include/linux/mfd/da9055/reg.h:1: error: stray ‘\357’ in program
      include/linux/mfd/da9055/reg.h:1: error: stray ‘\273’ in program
      include/linux/mfd/da9055/reg.h:1: error: stray ‘\277’ in program
      
      Remove the BOMs, the rest of the files is plain ASCII anyway.
      
      Output of "file" before:
      
      include/linux/mfd/da9055/core.h:  UTF-8 Unicode (with BOM) C program text
      include/linux/mfd/da9055/pdata.h: UTF-8 Unicode (with BOM) C program text
      include/linux/mfd/da9055/reg.h:   UTF-8 Unicode (with BOM) C program text
      
      Output of "file" after:
      
      include/linux/mfd/da9055/core.h:  ASCII C program text
      include/linux/mfd/da9055/pdata.h: ASCII C program text
      include/linux/mfd/da9055/reg.h:   ASCII C program text
      Signed-off-by: default avatarGeert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      90a38d99
    • Lee Jones's avatar
      mfd: Provide the STMPE driver with its own IRQ domain · 76f93992
      Lee Jones authored
      
      The STMPE driver is yet another IRQ controller which requires its
      own IRQ domain. So, we provide it with one.
      Acked-by: default avatarArnd Bergmann <arnd@arndb.de>
      Acked-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarLee Jones <lee.jones@linaro.org>
      Signed-off-by: default avatarSamuel Ortiz <sameo@linux.intel.com>
      76f93992
  5. 08 Nov, 2012 1 commit
  6. 05 Nov, 2012 5 commits
  7. 02 Nov, 2012 1 commit
  8. 31 Oct, 2012 2 commits
    • Xiao Guangrong's avatar
      KVM: x86: fix vcpu->mmio_fragments overflow · 87da7e66
      Xiao Guangrong authored
      After commit b3356bf0
      
       (KVM: emulator: optimize "rep ins" handling),
      the pieces of io data can be collected and write them to the guest memory
      or MMIO together
      
      Unfortunately, kvm splits the mmio access into 8 bytes and store them to
      vcpu->mmio_fragments. If the guest uses "rep ins" to move large data, it
      will cause vcpu->mmio_fragments overflow
      
      The bug can be exposed by isapc (-M isapc):
      
      [23154.818733] general protection fault: 0000 [#1] SMP DEBUG_PAGEALLOC
      [ ......]
      [23154.858083] Call Trace:
      [23154.859874]  [<ffffffffa04f0e17>] kvm_get_cr8+0x1d/0x28 [kvm]
      [23154.861677]  [<ffffffffa04fa6d4>] kvm_arch_vcpu_ioctl_run+0xcda/0xe45 [kvm]
      [23154.863604]  [<ffffffffa04f5a1a>] ? kvm_arch_vcpu_load+0x17b/0x180 [kvm]
      
      Actually, we can use one mmio_fragment to store a large mmio access then
      split it when we pass the mmio-exit-info to userspace. After that, we only
      need two entries to store mmio info for the cross-mmio pages access
      Signed-off-by: default avatarXiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
      Signed-off-by: default avatarMarcelo Tosatti <mtosatti@redhat.com>
      87da7e66
    • Konrad Rzeszutek Wilk's avatar
      xen/mmu: Use Xen specific TLB flush instead of the generic one. · 95a7d768
      Konrad Rzeszutek Wilk authored
      
      As Mukesh explained it, the MMUEXT_TLB_FLUSH_ALL allows the
      hypervisor to do a TLB flush on all active vCPUs. If instead
      we were using the generic one (which ends up being xen_flush_tlb)
      we end up making the MMUEXT_TLB_FLUSH_LOCAL hypercall. But
      before we make that hypercall the kernel will IPI all of the
      vCPUs (even those that were asleep from the hypervisor
      perspective). The end result is that we needlessly wake them
      up and do a TLB flush when we can just let the hypervisor
      do it correctly.
      
      This patch gives around 50% speed improvement when migrating
      idle guest's from one host to another.
      
      Oracle-bug: 14630170
      
      CC: stable@vger.kernel.org
      Tested-by: default avatarJingjie Jiang <jingjie.jiang@oracle.com>
      Suggested-by: default avatarMukesh Rathor <mukesh.rathor@oracle.com>
      Signed-off-by: default avatarKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      95a7d768
  9. 30 Oct, 2012 1 commit
  10. 28 Oct, 2012 2 commits
  11. 26 Oct, 2012 1 commit
    • Johannes Berg's avatar
      mac80211: verify that skb data is present · 9b395bc3
      Johannes Berg authored
      
      A number of places in the mesh code don't check that
      the frame data is present and in the skb header when
      trying to access. Add those checks and the necessary
      pskb_may_pull() calls. This prevents accessing data
      that doesn't actually exist.
      
      To do this, export ieee80211_get_mesh_hdrlen() to be
      able to use it in mac80211.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      9b395bc3
  12. 25 Oct, 2012 1 commit
  13. 24 Oct, 2012 4 commits