Skip to content
  • Shivaprasad G Bhat's avatar
    ee3a71e3
    spapr: Add NVDIMM device support · ee3a71e3
    Shivaprasad G Bhat authored
    
    
    Add support for NVDIMM devices for sPAPR. Piggyback on existing nvdimm
    device interface in QEMU to support virtual NVDIMM devices for Power.
    Create the required DT entries for the device (some entries have
    dummy values right now).
    
    The patch creates the required DT node and sends a hotplug
    interrupt to the guest. Guest is expected to undertake the normal
    DR resource add path in response and start issuing PAPR SCM hcalls.
    
    The device support is verified based on the machine version unlike x86.
    
    This is how it can be used ..
    Ex :
    For coldplug, the device to be added in qemu command line as shown below
    -object memory-backend-file,id=memnvdimm0,prealloc=yes,mem-path=/tmp/nvdimm0,share=yes,size=1073872896
    -device nvdimm,label-size=128k,uuid=75a3cdd7-6a2f-4791-8d15-fe0a920e8e9e,memdev=memnvdimm0,id=nvdimm0,slot=0
    
    For hotplug, the device to be added from monitor as below
    object_add memory-backend-file,id=memnvdimm0,prealloc=yes,mem-path=/tmp/nvdimm0,share=yes,size=1073872896
    device_add nvdimm,label-size=128k,uuid=75a3cdd7-6a2f-4791-8d15-fe0a920e8e9e,memdev=memnvdimm0,id=nvdimm0,slot=0
    
    Signed-off-by: default avatarShivaprasad G Bhat <sbhat@linux.ibm.com>
    Signed-off-by: default avatarBharata B Rao <bharata@linux.ibm.com>
                   [Early implementation]
    Message-Id: <158131058078.2897.12767731856697459923.stgit@lep8c.aus.stglabs.ibm.com>
    Signed-off-by: default avatarDavid Gibson <david@gibson.dropbear.id.au>
    ee3a71e3
    spapr: Add NVDIMM device support
    Shivaprasad G Bhat authored
    
    
    Add support for NVDIMM devices for sPAPR. Piggyback on existing nvdimm
    device interface in QEMU to support virtual NVDIMM devices for Power.
    Create the required DT entries for the device (some entries have
    dummy values right now).
    
    The patch creates the required DT node and sends a hotplug
    interrupt to the guest. Guest is expected to undertake the normal
    DR resource add path in response and start issuing PAPR SCM hcalls.
    
    The device support is verified based on the machine version unlike x86.
    
    This is how it can be used ..
    Ex :
    For coldplug, the device to be added in qemu command line as shown below
    -object memory-backend-file,id=memnvdimm0,prealloc=yes,mem-path=/tmp/nvdimm0,share=yes,size=1073872896
    -device nvdimm,label-size=128k,uuid=75a3cdd7-6a2f-4791-8d15-fe0a920e8e9e,memdev=memnvdimm0,id=nvdimm0,slot=0
    
    For hotplug, the device to be added from monitor as below
    object_add memory-backend-file,id=memnvdimm0,prealloc=yes,mem-path=/tmp/nvdimm0,share=yes,size=1073872896
    device_add nvdimm,label-size=128k,uuid=75a3cdd7-6a2f-4791-8d15-fe0a920e8e9e,memdev=memnvdimm0,id=nvdimm0,slot=0
    
    Signed-off-by: default avatarShivaprasad G Bhat <sbhat@linux.ibm.com>
    Signed-off-by: default avatarBharata B Rao <bharata@linux.ibm.com>
                   [Early implementation]
    Message-Id: <158131058078.2897.12767731856697459923.stgit@lep8c.aus.stglabs.ibm.com>
    Signed-off-by: default avatarDavid Gibson <david@gibson.dropbear.id.au>
Loading