agp(4): release unbinded memory

2012-11-13 Thread Martin Pieuchot
While experimenting with the agp(4) interface I found that if you release the interface (AGPIOC_RELEASE) before closing its file descriptor you'll end up with allocated but unbinded memory blocks. This behavior is due to the fact that the agp_release_helper() function doesn't free the memory

Re: agp(4): release unbinded memory

2012-11-13 Thread Mark Kettenis
Date: Tue, 13 Nov 2012 12:30:29 +0100 From: Martin Pieuchot mpieuc...@nolizard.org While experimenting with the agp(4) interface I found that if you release the interface (AGPIOC_RELEASE) before closing its file descriptor you'll end up with allocated but unbinded memory blocks. That

Re: agp(4): release unbinded memory

2012-11-13 Thread Martin Pieuchot
On 13/11/12(Tue) 13:45, Mark Kettenis wrote: Date: Tue, 13 Nov 2012 12:30:29 +0100 From: Martin Pieuchot mpieuc...@nolizard.org While experimenting with the agp(4) interface I found that if you release the interface (AGPIOC_RELEASE) before closing its file descriptor you'll end up

Re: agp(4): release unbinded memory

2012-11-13 Thread Mark Kettenis
Date: Tue, 13 Nov 2012 16:15:59 +0100 From: Martin Pieuchot mpieuc...@nolizard.org On 13/11/12(Tue) 13:45, Mark Kettenis wrote: Date: Tue, 13 Nov 2012 12:30:29 +0100 From: Martin Pieuchot mpieuc...@nolizard.org While experimenting with the agp(4) interface I found that if you