habanalabs: de-couple MMU and VM module initialization

Browse source

This patch initializes the MMU S/W structures before the VM S/W
structures, instead of doing that as part of the VM S/W initialization.

This is done because we need to configure some MMU mappings for the kernel
context, before the VM is initialized. The VM initialization can't be
moved earlier because it depends on the size of the DRAM, which is
retrieved from the device CPU. Communication with the device CPU will
require the MMU mappings to be configured and hence the de-coupling.

Signed-off-by: Oded Gabbay <oded.gabbay@gmail.com>

...

This commit is contained in:

Oded Gabbay 2019-05-29 14:43:04 +03:00

parent 0b28d26b9d

commit 37d68ce527

3 changed files with 22 additions and 20 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

23

drivers/misc/habanalabs/device.c

View file

13

drivers/misc/habanalabs/memory.c

View file

6

drivers/misc/habanalabs/mmu.c

View file