summaryrefslogtreecommitdiff
path: root/drivers/scsi/cxlflash/main.c
diff options
context:
space:
mode:
authorUma Krishnan <ukrishn@linux.vnet.ibm.com>2016-03-04 21:55:18 (GMT)
committerMartin K. Petersen <martin.petersen@oracle.com>2016-03-09 02:17:33 (GMT)
commit5d1952acd0d56f6b6835aa45bea763ee97b9e66f (patch)
treef37166e34c555d2c106efd20de6bcd369f0049e5 /drivers/scsi/cxlflash/main.c
parent8a96b52af58721caf4f7496d0737e8ec6b63c86e (diff)
downloadlinux-5d1952acd0d56f6b6835aa45bea763ee97b9e66f.tar.xz
cxlflash: Reorder user context initialization
In order to support cxlflash in the PowerVM environment, underlying hypervisor APIs have imposed a kernel API ordering change. For the superpipe access to LUN, user applications need a context. The cxlflash module creates this context by making a sequence of cxl calls. In the current code, a context is initialized via cxl_dev_context_init() followed by cxl_process_element(), a function that obtains the process element id. Finally, cxl_start_work() is called to attach the process element. In the PowerVM environment, a process element id cannot be obtained from the hypervisor until the process element is attached. The cxlflash module is unable to create contexts without a valid process element id. To fix this problem, cxl_start_work() is called before obtaining the process element id. Signed-off-by: Uma Krishnan <ukrishn@linux.vnet.ibm.com> Acked-by: Matthew R. Ochs <mrochs@linux.vnet.ibm.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/scsi/cxlflash/main.c')
0 files changed, 0 insertions, 0 deletions