Hi, Dave,
It is the explanation that is inaccurate; I was still thinking about mmap when
the new paradigm is to do the mapping when the VM faults.
I believe the code that requires this patch is: ttm/ttm_bo_vm.c:
ttm_bo_vm_fault(),
specifically:
for (i = 0; i < TTM_BO_VM_NUM_PREFAULT; ++i) {
Hi, Dave,
It is the explanation that is inaccurate; I was still thinking about mmap when
the new paradigm is to do the mapping when the VM faults.
I believe the code that requires this patch is: ttm/ttm_bo_vm.c:
ttm_bo_vm_fault(),
specifically:
for (i = 0; i < TTM_BO_VM_NUM_PREFAULT; ++i) {
On Fri, Jun 10, 2011 at 8:20 AM, Jay Estabrook
wrote:
>
> Alpha needs to have the system bus address for the device's local
> memory available, so that it can be returned to user-level, where
> it may be used in an mmap(). So, we make bus.addr hold the ioremap()
> return for kernel use, and then
On Fri, Jun 10, 2011 at 8:20 AM, Jay Estabrook wrote:
>
> Alpha needs to have the system bus address for the device's local
> memory available, so that it can be returned to user-level, where
> it may be used in an mmap(). So, we make bus.addr hold the ioremap()
> return for kernel use, and then w
Alpha needs to have the system bus address for the device's local
memory available, so that it can be returned to user-level, where
it may be used in an mmap(). So, we make bus.addr hold the ioremap()
return for kernel use, and then we can modify bus.base appropriately.
Signed-off-by: Jay Estabro
Alpha needs to have the system bus address for the device's local
memory available, so that it can be returned to user-level, where
it may be used in an mmap(). So, we make bus.addr hold the ioremap()
return for kernel use, and then we can modify bus.base appropriately.
Signed-off-by: Jay Estabro
