Having the configuration option CONFIG_HAVE_ARCH_VMAP_STACK set to y causes s-Par to fail to boot properly.
The root issue is that you are not allowed to have items on the stack being passed to "DMA" like operations. In this case we have a vmcall and a inline completion of a scsi command.
The github branch vmap_stack_hack has two patches that allow us to boot but they are HACKs. We should be doing this in a more appropriate way, and now that we have a visorchipset_dev we should be able to use that to help store visorchipet information (vmcall params).
Kanboard:28012
Having the configuration option CONFIG_HAVE_ARCH_VMAP_STACK set to y causes s-Par to fail to boot properly.
The root issue is that you are not allowed to have items on the stack being passed to "DMA" like operations. In this case we have a vmcall and a inline completion of a scsi command.
The github branch vmap_stack_hack has two patches that allow us to boot but they are HACKs. We should be doing this in a more appropriate way, and now that we have a visorchipset_dev we should be able to use that to help store visorchipet information (vmcall params).