Page MenuHomeFreeBSD

nvme: Change devctl events for the controller
ClosedPublic

Authored by imp on Mar 4 2024, 11:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Apr 22, 11:14 PM
Unknown Object (File)
Sun, Apr 21, 7:42 AM
Unknown Object (File)
Sun, Apr 21, 7:42 AM
Unknown Object (File)
Sun, Apr 21, 7:41 AM
Unknown Object (File)
Sun, Apr 21, 7:41 AM
Unknown Object (File)
Fri, Apr 19, 6:26 PM
Unknown Object (File)
Mar 13 2024, 4:30 AM
Unknown Object (File)
Mar 7 2024, 4:33 AM
Subscribers

Details

Summary

Change the devctl events slightly for the controller. SMART errors will
log the changed bits in the NVME SMART Critical Warning State as its
event.

Reset will now emit 'event=start'. Soon more.

Sponsored by: Netflix

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

sys/dev/nvme/nvme_ctrlr.c
67–69

I see no space between the parameters neither here nor in the callers.

670

I wonder how convenient is it to handle the state bitmask in devd.conf.

This revision is now accepted and ready to land.Mar 6 2024, 2:16 PM
This revision was automatically updated to reflect the committed changes.
sys/dev/nvme/nvme_ctrlr.c
670

I think it will be clear enough. State tells you chat changed, and the log page 0 tells you whats' currently active. some amount of parsing by a script will be needed to sort out what's new and what's old anyway, so I think in practice it won't be too bad. If I'm wrong, I'll figure out what to do then... I've thought in the past of augmenting devd.conf to allow better numeric expressions. But if there's ever a good use case for ucl, I think devd.conf might be it.... But both of those are beyond the scope of this change.