linux-toradex.git/drivers/char/agp/backend.c, branch v2.6.27.25

intel/agp: rewrite GTT on resume

2008-08-12T00:13:38+00:00

On my Intel chipset (965GM), the GTT is entirely erased across
suspend/resume.  This patch simply re-plays the current mapping at resume
time to restore the table.=20

I noticed this once I started relying on persistent GTT mappings across VT
switch in our GEM work -- the old X server and DRM code carefully unbind
all memory from the GTT on VT switch, but GEM does not bother.

I placed the list management and rewrite code in the generic layer on the
assumption that it will be needed on other hardware, but I did not add the
rewrite call to anything other than the Intel resume function.

Keep a list of current GATT mappings.  At resume time, rewrite them into
the GATT.  This is needed on Intel (at least) as the entire GATT is
cleared across suspend/resume.

[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Keith Packard 
Cc: Dave Jones 
Cc: Andi Kleen 
Signed-off-by: Andrew Morton 
Signed-off-by: Dave Airlie

agp: use dev_printk when possible

2008-08-12T00:13:38+00:00

Convert printks to use dev_printk().

Signed-off-by: Bjorn Helgaas 
Signed-off-by: Andrew Morton 
Signed-off-by: Dave Airlie

agp: two-stage page destruction issue

2008-06-18T23:56:16+00:00

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: Dave Airlie

agp: add chipset flushing support to AGP interface

2008-02-05T04:33:32+00:00

This bumps the AGP interface to 0.103.

Certain Intel chipsets contains a global write buffer, and this can require
flushing from the drm or X.org to make sure all data has hit RAM before
initiating a GPU transfer, due to a lack of coherency with the integrated
graphics device and this buffer.

This just adds generic support to the AGP interfaces, a follow-on patch
will add support to the Intel driver to use this interface.

Signed-off-by: Dave Airlie

x86: remove flush_agp_mappings()

2008-01-30T12:34:07+00:00

Signed-off-by: Ingo Molnar 
Signed-off-by: Thomas Gleixner

AGP fix race condition between unmapping and freeing pages

2007-10-15T00:32:15+00:00

With Andi's clflush fixup, we were getting hangs on server exit, flushing the
mappings after freeing each page helped.

This showed up a race condition where the pages after being freed could be
reused before the agp mappings had been flushed.  Flushing after each single
page is a bad thing for future drm work, so make the page destroy a two pass
unmapping all the pages, flushing the mappings, and then destroying the pages.

Signed-off-by: Dave Airlie 
Signed-off-by: Andrew Morton

[AGPGART] Hand off AGP maintainence.

2007-07-10T00:23:50+00:00

Most of the AGP changes recently have been done in lock-step with
DRM updates, so it's probably easier to have airlied pushing
AGP changes at the same time he does DRM updates.

[Also remove my name from the boot messages.
 Cautionary tale to others: Never do this, when computers
 don't boot, people assume you're responsible even if 15
 other subsystems initialised after yours. :-) ]

Signed-off-by: Dave Jones 
Signed-off-by: Dave Airlie

[AGPGART] Allow drm-populated agp memory types

2007-02-03T22:16:24+00:00

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: Thomas Hellstrom 
Signed-off-by: Dave Jones

[AGPGART] Const'ify the agpgart driver version.

2006-08-11T22:02:27+00:00

Signed-off-by: Dave Jones

[AGPGART] Lots of CodingStyle/whitespace cleanups.

2006-02-28T05:54:25+00:00

Eliminate trailing whitespace.
s/if(/if (/
s/for(/for (/

Signed-off-by: Dave Jones