Use ${PWD}

Follow jlduran's suggestion of using atf_check -r.

Which revision removed these?

To be clear, the point is to have an explicit panic rather than a boot hang because we end up spinning in an uninitialized trap handler?

Always open /dev/pci read-write.

In D54753#1251493, @minsoochoo0122_proton.me wrote:

In D54753#1251492, @markj wrote:

In D54753#1251486, @minsoochoo0122_proton.me wrote:

This is really just an argument for moving away from C entirely. And I'd quite like that personally, but it's easier said than done.

My original implementation of minmax caching on wavl (using prev and next) always failed CI build on github,

In D54753#1251486, @minsoochoo0122_proton.me wrote:

In D54753#1251467, @markj wrote:

To be honest, I'm not thrilled to have a whole new set of functions for doing something already covered by queue.h and used extensively throughout the tree. These functions don't provide any type checking or debug assertions/poisoning like the queue.h macros do. These functions might be easier to use for someone not used to queue.h, but there are tons of examples of queue.h macro usage in the tree to draw from.

Type checking is done here and there is no need for (void *) casting. containerof() will return the structure that contains the node and other data. For assertion, we can let users to declare their own assert functions and call it in the headers, but I forgot to implement it here.

To be honest, I'm not thrilled to have a whole new set of functions for doing something already covered by queue.h and used extensively throughout the tree. These functions don't provide any type checking or debug assertions/poisoning like the queue.h macros do. These functions might be easier to use for someone not used to queue.h, but there are tons of examples of queue.h macro usage in the tree to draw from.