Page MenuHomeFreeBSD

loader: simplify efi_zfs_probe and avoid double probing for zfs.
ClosedPublic

Authored by tsoome on Mar 30 2017, 12:24 PM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 22 2023, 10:53 PM
Unknown Object (File)
Nov 5 2023, 5:46 AM
Unknown Object (File)
Jul 15 2023, 9:36 PM
Unknown Object (File)
Jul 15 2023, 9:19 PM
Unknown Object (File)
Jul 5 2023, 5:51 AM
Unknown Object (File)
May 12 2023, 2:09 PM
Subscribers
None

Details

Summary

The current efi_zfs_probe() is overcomplicated and can be made
simpler. Still we need to pick up the device handle for our boot
disk first, because the ESP does not have to be the first partition on the
disk.

Once we do have the handle for boot disk, we probe that this with
pointer for pool GUID.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Does this change which pool might be booted from if you have more than 1 pool?

How have you tested this change?

Does this change which pool might be booted from if you have more than 1 pool?

How have you tested this change?

The first found pool from the boot disk will be booted - I mean, we still do use the device handle from loaded image and use it to read out the boot pool GUID, just using much less complicated way. Testing is the usual - build/boot; also the same implementation is used in my illumos loader port and ok, I do not have multiple pools on the same disk, but I do have multiple pools on different disks in my test VM. So far i haven't seen anything unexpected.

This revision is now accepted and ready to land.Mar 30 2017, 4:01 PM
This revision was automatically updated to reflect the committed changes.