Skip to content
  1. Nov 18, 2010
    • Giuseppe CAVALLARO's avatar
      sh: Use GCC __builtin_prefetch() to implement prefetch(). · d53e4307
      Giuseppe CAVALLARO authored
      
      
      GCC's __builtin_prefetch() was introduced a long time ago, all
      supported GCC versions have it. So this patch is to use it for
      implementing the prefetch on SH2A and SH4.
      
      The current  prefetch implementation is almost equivalent with
      __builtin_prefetch.
      The third parameter in the __builtin_prefetch is the locality
      that it's not supported on SH architectures.  It has been set
      to three and it should be verified if it's suitable for SH2A
      as well. I didn't test on this architecture.
      
      The builtin usage should be more efficient that an __asm__
      because less barriers, and because the compiler doesn't see the
      inst as a "black box" allowing better code generation.
      
      This has been already done on other architectures (see the commit:
      0453fb3c).
      
      Many thanks to Christian Bruel <christain.bruel@st.com> for his
      support on evaluate the impact of the gcc built-in on SH4 arch.
      
      No regressions found while testing with LMbench on STLinux targets.
      
      Signed-off-by: default avatarGiuseppe Cavallaro <peppe.cavallaro@st.com>
      Signed-off-by: default avatarStuart Menefy <stuart.menefy@st.com>
      Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
      d53e4307
  2. Nov 17, 2010
  3. Nov 15, 2010
  4. Nov 13, 2010
  5. Nov 12, 2010
  6. Nov 11, 2010
    • Bjorn Helgaas's avatar
      x86/PCI: coalesce overlapping host bridge windows · 4723d0f2
      Bjorn Helgaas authored
      Some BIOSes provide PCI host bridge windows that overlap, e.g.,
      
          pci_root PNP0A03:00: host bridge window [mem 0xb0000000-0xffffffff]
          pci_root PNP0A03:00: host bridge window [mem 0xafffffff-0xdfffffff]
          pci_root PNP0A03:00: host bridge window [mem 0xf0000000-0xffffffff]
      
      If we simply insert these as children of iomem_resource, the second window
      fails because it conflicts with the first, and the third is inserted as a
      child of the first, i.e.,
      
          b0000000-ffffffff PCI Bus 0000:00
            f0000000-ffffffff PCI Bus 0000:00
      
      When we claim PCI device resources, this can cause collisions like this
      if we put them in the first window:
      
          pci 0000:00:01.0: address space collision: [mem 0xff300000-0xff4fffff] conflicts with PCI Bus 0000:00 [mem 0xf0000000-0xffffffff]
      
      Host bridge windows are top-level resources by definition, so it doesn't
      make sense to make the third window a child of the first.  This patch
      coalesces any host bridge windows that overlap.  For the example above,
      the result is this single window:
      
          pci_root PNP0A03:00: host bridge window [mem 0xafffffff-0xffffffff]
      
      This fixes a 2.6.34 regression.
      
      Reference: https://bugzilla.kernel.org/show_bug.cgi?id=17011
      
      
      Reported-and-tested-by: default avatarAnisse Astier <anisse@astier.eu>
      Reported-and-tested-by: default avatarPramod Dematagoda <pmd.lotr.gandalf@gmail.com>
      Signed-off-by: default avatarBjorn Helgaas <bjorn.helgaas@hp.com>
      Signed-off-by: default avatarJesse Barnes <jbarnes@virtuousgeek.org>
      4723d0f2
    • Ian Campbell's avatar
      xen: do not release any memory under 1M in domain 0 · 9ec23a7f
      Ian Campbell authored
      
      
      We already deliberately setup a 1-1 P2M for the region up to 1M in
      order to allow code which assumes this region is already mapped to
      work without having to convert everything to ioremap.
      
      Domain 0 should not return any apparently unused memory regions
      (reserved or otherwise) in this region to Xen since the e820 may not
      accurately reflect what the BIOS has stashed in this region.
      
      Signed-off-by: default avatarIan Campbell <ian.campbell@citrix.com>
      Signed-off-by: default avatarJeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
      9ec23a7f
  7. Nov 10, 2010
  8. Nov 09, 2010
    • Andi Kleen's avatar
      x86: Address gcc4.6 "set but not used" warnings in apic.h · 0059b243
      Andi Kleen authored
      
      
      native_apic_msr_read() and x2apic_enabled() use rdmsr(msr, low, high),
      but only use the low part.
      
      gcc4.6 complains about this:
      .../apic.h:144:11: warning: variable 'high' set but not used [-Wunused-but-set-variable]
      
      rdmsr() is just a wrapper around rdmsrl() which splits the 64bit value
      into low and high, so using rdmsrl() directly solves this.
      
      [tglx: Changed the variables to u64 as suggested by Cyrill. It's less
             confusing and has no code impact as this is 64bit only anyway.
             Massaged changelog as well. ]
      
      Signed-off-by: default avatarAndi Kleen <ak@linux.intel.com>
      Cc: x86@kernel.org
      Cc: Cyrill Gorcunov <gorcunov@gmail.com>
      LKML-Reference: <1289251229-19589-1-git-send-email-andi@firstfloor.org>
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      0059b243
    • Felipe Balbi's avatar
      arm: omap1: devices: need to return with a value · dfcccd3a
      Felipe Balbi authored
      
      
      Get rid of the following warning:
      
      arch/arm/mach-omap1/devices.c: In function 'omap_init_wdt':
      arch/arm/mach-omap1/devices.c:298: warning: 'return' with
      no value, in function returning non-void
      
      while at that, also change:
      
      platform_device_register();
      return 0;
      
      into:
      
      return platform_device_register();
      
      Signed-off-by: default avatarFelipe Balbi <balbi@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      dfcccd3a
  9. Nov 08, 2010
  10. Nov 07, 2010
  11. Nov 05, 2010
Loading