> On 10. Jun 2023, at 07:52, Alexey Dokuchaev <[email protected]> wrote:
>
> On Wed, Apr 26, 2023 at 12:02:19PM -0600, Warner Losh wrote:
>> On Wed, Apr 26, 2023 at 11:24???AM Kyle Evans wrote:
>>> commit ce5a210997da3c4064cfe162e760379f1fa8b587
>>>
>>> openzfs: arm64: implement kfpu_begin/kfpu_end
>>>
>>> This is part one of a fix for booting with ZFS on arm64 using
>>> accelerated checksum implementations. Checksum benchmarking will
>>> attempt to use the FPU, so we currently panic quickly on boot.
>>>
>>> Note that _STANDALONE is special-cased here, but ideally we
>>> wouldn't be building the code that uses kfpu_begin()/kfpu_end()
>>> at all in the loader environment.
>>
>> Yes. As noted elsewhere, the upstream is a mess. There's no way to
>> say "I only want the generic implementation" for these functions.
>> So we went through some crazy hoops to try to disable that... only
>> to run into a buzz-saw of upstream changes that broke the crazy hoops
>
> Sorry for not replying earlier, but given the situation with ZoL and
> how they keep breaking stuff for us, how feasible would it be to switch
> back to normal (illumos) ZFS?
>
> ./danfe
The normal (illumos) ZFS is struggling to get updates [from OpenZFS]. I know,
because I’m one who is trying to get them done:D
Situation is not encouraging, but I think the only way to make this situation
better is to try to work with OpenZFS team to improve how the things are done…
rgds,
toomas
