-
Woodstocktsoome: are you currently working on that 4k sector size issue with pcfs and uefi boot?
-
tsoomeyes
-
Woodstockgood
-
Woodstockthat means I don't have to
-
Woodstock:)
-
tsoome:)
-
Woodstockthe biggest issue i have with this is the silent failure to boot after installing. no error or warning or anything from the installer, or even from "zpool create -B"...
-
tsoomeI need to verify my patch for installboot, but its a bit complicated because I'm not really sure about pcfs writes:D
-
tsoomeand our mkfs does not support 4k sector size, so other tool is needed to create the fs...
-
tsoomeand, it seems we may need to reserve more 4k sectors with zpool create -B... so there are some traps hiding...
-
Woodstockwhy not update mkfs?
-
tsoomethats in process:) but the thing is, need to do with hand in hand of fsck, to be able to verify both created structure on disk and pcfs writes into it:D
-
tsoomeso far I have been attempting to verify by using fbsd fsck, but tbh, I'm not quite sure how much it can be trusted either:D
-
tsoomeanyhow, need to fix this memlist merge first....
-
antranigvI see that 1425,5801 is not available in illumos, it's a Chelsio Virtual Function (VF) device from SR-IOV. I was wondering, do we have a device that supports VF? I'd like to have a look at the code and try to implement it in t4nex/cxgbe
-
rmustaccIn this case the question of differences would be really Chelsio specific. I think the thing to do here is to understand how they handle VFs for this device on other systems.
-
rmustaccThere shouldn't be anything different in PCIe land here. But the issue will be that I presume you have to skip certain firmware related activities.
-
rmustaccDepending on how Chelsio has designed things and what's passed through in the VF bars it'll vary dramatically.