Balancing ttm_mem_io_reserve() and ttm_mem_io_free()
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Balancing ttm_mem_io_reserve() and ttm_mem_io_free()
- From: Thomas Hellström <thomas.hellstrom@xxxxxxxxxxxxxxx>
- Date: Fri, 19 Aug 2022 10:13:53 +0200
- Cc: DRI Development <dri-devel@xxxxxxxxxxxxxxxxxxxxx>
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0
Hi Christian,
I'm looking for a way to take some sort of reference across possible
VRAM accesses over the PCI bar, be it for runtime PM, workarounds or
whatever.
The ttm_mem_io_reserve/free seems like a good candidate, but is
completely unbalanced and looks racy. In particular error paths forget
to call ttm_mem_io_free().
Would you have any objections if I took a look at attempting to balance
calls to those functions, or do you have any other suggestions for a
better method?
Thanks,
Thomas
[Index of Archives]
[Linux DRI Users]
[Linux Intel Graphics]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Yosemite News]
[Linux Kernel]
[Linux SCSI]
[XFree86]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Linux Kernel]
[Linux SCSI]
[XFree86]