-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ofpathname: add support for NVMe logical/OpenFirmware device path conversion #3
Conversation
…vices Add support to convert logical device path to Open firmware device path for NVMe devices. Signed-off-by: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
…vices Add support to convert a Open Firmware device path to logical device path for NVMe devices (with namespace id). Signed-off-by: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
|
Hi Nathan, Have you had a chance to check this one? Here's some more testing w/ 2 NVMe adapters in a system. All good. OpenFirmware device-tree listing (2 NVMe adapters): Linux device listing (2 NVMe adapters, each w/ 1 namespace w/ 3 partitions) nvme_l2of() nvme_of2l(): Test: OF boot-device set by grub-install: |
|
Hi Mauricio, I added these patches to the -next branch, they will be merged into the master branch when I push out the next release. -Nathan |
|
Hi Nathan, Okay, thanks!
|
These 2 patches add the functions
of2l_nvme()andl2of_nvme()toscripts/ofpathname.Test scenario:
Test results:
l2of_nvme()Existing devices:
Non-existing devices:
of2l_nvme()Existing devices:
The case without a namespace ID (above) can not be handled
as there's not enough information available in the OpenFirmware
device path nor device-tree in order to match it uniquely to a
nvmeX device path.
Anything with a namespace ID (below) has enough information and works:
Non-existing devices:
Thanks: Colleen Stouffer, for technical advice and hardware availability.