1. 18 Jun, 2008 1 commit
    • Jan Beulich's avatar
      agp: two-stage page destruction issue · da503fa6
      Jan Beulich authored
      
      
      besides it apparently being useful only in 2.6.24 (the changes in 2.6.25
      really mean that it could be converted back to a single-stage mechanism),
      I'm seeing an issue in Xen Dom0 kernels, which is caused by the calling
      of gart_to_virt() in the second stage invocations of the destroy function.
      I think that besides this being a real issue with Xen (where
      unmap_page_from_agp() is not just a page table attribute change), this
      also is invalid from a theoretical perspective: One should not assume that
      gart_to_virt() is still valid after unmapping a page. So minimally (keeping
      the 2-stage mechanism) a patch like the one below would be needed.
      
      Jan
      
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      da503fa6
  2. 04 Feb, 2008 8 commits
  3. 30 Jan, 2008 2 commits
  4. 23 Jan, 2008 1 commit
  5. 14 Oct, 2007 1 commit
  6. 06 Oct, 2007 1 commit
  7. 19 Sep, 2007 1 commit
  8. 11 Sep, 2007 2 commits
  9. 25 Aug, 2007 1 commit
    • Scott Thompson's avatar
      agp: balance ioremap checks · 5bdbc7dc
      Scott Thompson authored
      
      
      patchset against 2.6.23-rc3.
      corrects missing ioremap return checks and balancing on iounmap calls, integrated changes per list
      recommendations on the original set of patches..
      
      Signed-off-by: Scott Thompson <postfail <at> hushmail.com>
      Signed-off-by: default avatarDave Airlie <airlied@linux.ie>
      5bdbc7dc
  10. 26 Jul, 2007 2 commits
  11. 21 Jun, 2007 1 commit
  12. 14 Jun, 2007 1 commit
  13. 06 Jun, 2007 5 commits
  14. 26 Apr, 2007 1 commit
  15. 09 Apr, 2007 1 commit
  16. 08 Apr, 2007 1 commit
  17. 22 Feb, 2007 1 commit
  18. 10 Feb, 2007 1 commit
  19. 06 Feb, 2007 1 commit
  20. 04 Feb, 2007 1 commit
  21. 03 Feb, 2007 1 commit
    • Thomas Hellstrom's avatar
      [AGPGART] Allow drm-populated agp memory types · a030ce44
      Thomas Hellstrom authored
      
      
      This patch allows drm to populate an agpgart structure with pages of its own.
      It's needed for the new drm memory manager which dynamically flips pages in and out of AGP.
      
      The patch modifies the generic functions as well as the intel agp driver. The intel drm driver is
      currently the only one supporting the new memory manager.
      
      Other agp drivers may need some minor fixing up once they have a corresponding memory manager enabled drm driver.
      
      AGP memory types >= AGP_USER_TYPES are not populated by the agpgart driver, but the drm is expected
      to do that, as well as taking care of cache- and tlb flushing when needed.
      
      It's not possible to request these types from user space using agpgart ioctls.
      
      The Intel driver also gets a new memory type for pages that can be bound cached to the intel GTT.
      
      Signed-off-by: default avatarThomas Hellstrom <thomas@tungstengraphics.com>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      a030ce44
  22. 16 Jan, 2007 1 commit
  23. 28 Dec, 2006 1 commit
  24. 22 Dec, 2006 2 commits
    • Eric Anholt's avatar
      [AGPGART] fix detection of aperture size versus GTT size on G965 · c41e0deb
      Eric Anholt authored
      
      
      On the G965, the GTT size may be larger than is required to cover the
      aperture.  (In fact, on all hardware we've seen, the GTT is 512KB to the
      aperture's 256MB).  A previous commit forced the aperture size to 512MB on
      G965 to match GTT, which would likely result in hangs at best if users
      tried to rely on agpgart's aperture size information.  Instead, we use the
      resource length for the aperture size and the system's reported GTT size
      when available for the GTT size.
      
      Because the MSAC registers which had been read for aperture size detection
      on i9xx chips just cause a change in the resource size, we can use generic
      code for aperture detection on all i9xx.
      
      Signed-off-by: default avatarEric Anholt <eric@anholt.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      c41e0deb
    • Thomas Hellstrom's avatar
      [AGPGART] Remove unnecessary flushes when inserting and removing pages. · 5aa80c72
      Thomas Hellstrom authored
      
      
      This patch is to speed up flipping of pages in and out of the AGP aperture as
      needed by the new drm memory manager.
      
      A number of global cache flushes are removed as well as some PCI posting flushes.
      The following guidelines have been used:
      
      1) Memory that is only mapped uncached and that has been subject to a global
      cache flush after the mapping was changed to uncached does not need any more
      cache flushes. Neither before binding to the aperture nor after unbinding.
      
      2) Only do one PCI posting flush after a sequence of writes modifying page
      entries in the GATT.
      
      Signed-off-by: default avatarThomas Hellstrom <thomas@tungstengraphics.com>
      Signed-off-by: default avatarDave Jones <davej@redhat.com>
      5aa80c72
  25. 22 Nov, 2006 1 commit
    • Linus Torvalds's avatar
      [AGP] Allocate AGP pages with GFP_DMA32 by default · 66c669ba
      Linus Torvalds authored
      
      
      Not all graphic page remappers support physical addresses over the 4GB
      mark for remapping, so while some do (the AMD64 GART always did, and I
      just fixed the i965 to do so properly), we're safest off just forcing
      GFP_DMA32 allocations to make sure graphics pages get allocated in the
      low 32-bit address space by default.
      
      AGP sub-drivers that really care, and can do better, could just choose
      to implement their own allocator (or we could add another "64-bit safe"
      default allocator for their use), but quite frankly, you're not likely
      to care in practice.
      
      So for now, this trivial change means that we won't be allocating pages
      that we can't map correctly by mistake on x86-64.
      
      [ On traditional 32-bit x86, this could never happen, because GFP_KERNEL
        would never allocate any highmem memory anyway ]
      
      Acked-by: default avatarAndi Kleen <ak@suse.de>
      Acked-by: default avatarDave Jones <davej@redhat.com>
      Cc: Eric Anholt <eric@anholt.net>
      Cc: Keith Packard <keithp@keithp.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      66c669ba