linux: Convert various API shims to use membar_release/acquire.

drm: Convert noisy flush_workqueue message to dtrace probe.

linux: Downgrade warning about flushing from workqueue to debug.

linux: Make flush_workqueue a noop if run from the workqueue.

I think this matches Linux semantics but this is very much not clear
and not written down anywhere obvious and why is this such a
semant

linux: Make flush_workqueue a noop if run from the workqueue.

I think this matches Linux semantics but this is very much not clear
and not written down anywhere obvious and why is this such a
semantically incoherent mess.

show more ...

linux: Fix flush_workqueue.

Simplify mechanism: we know there's only a single thread here that
processes scheduled work in FIFO order (no multi-CPU workqueues --
would have to adapt if there were),

linux: Fix flush_workqueue.

Simplify mechanism: we know there's only a single thread here that
processes scheduled work in FIFO order (no multi-CPU workqueues --
would have to adapt if there were), so just schedule a work item that
notifies of completion. The previous mechanism of counting 0, 1, or
2 generation numbers was broken by an earlier change to avoid abuse
of tailqs arising from clever TAILQ_CONCAT.

show more ...

linux: Update workqueue flush to reflect TAILQ_CONCAT change.

linux/workqueue: Draft queue_rcu_work.

linux/workqueue: Use atomic_load/store.

i915: another whack at it

alloc_workqueue

Constify work_pending, delayed_work_pending.

drain_workqueue

Add work_pending, delayed_work_pending.

Implement return value of flush_work, flush_delayed_work.

New system_unbound_wq.

Fix copypasta in error branch.

XXX pullup to HEAD

Fix abuse of TAILQ_CONCAT.

Other parts of this expect that the entries will be on wq->wq_queue
or wq->wq_dqueue, so we can't just move a batch of entries onto a
temporary queue. Instead, use a mark

Fix abuse of TAILQ_CONCAT.

Other parts of this expect that the entries will be on wq->wq_queue
or wq->wq_dqueue, so we can't just move a batch of entries onto a
temporary queue. Instead, use a marker node to delimit when the
batch ends.

XXX pullup

show more ...

- dwc2 need calling linux_workqueue_init() to avoid panic.
- use INIT_ONCE/FINI_ONCE to linux_workqueue_{init,fini}() for being called from dwc2.

TODO: dwc2 should be written as kernel module depeng

- dwc2 need calling linux_workqueue_init() to avoid panic.
- use INIT_ONCE/FINI_ONCE to linux_workqueue_{init,fini}() for being called from dwc2.

TODO: dwc2 should be written as kernel module depenging on a linux module.

show more ...

Workqueue lock must be at IPL_VM for use in interrupts, duh.

Don't skimp on the last batch of work when worker is dying.

This is capitalism. We can't afford to waste time the worker could
spend on labour even if we work 'em to death!

Sprinkle dtrace probes all over the Linux workqueue stuff.

Fix post-cancellation case of queue_delayed_work.

Request the callout queue immediately, as if it hadn't been cancelled
at all, rather than reschedule for the next tick.

Rework Linux workqueue synchronization yet again.

- Use a low bit in the pointer to the queue, rather than whether the
pointer is null or not, to determine whether the work item is
queued/schedu

Rework Linux workqueue synchronization yet again.

- Use a low bit in the pointer to the queue, rather than whether the
pointer is null or not, to determine whether the work item is
queued/scheduled.

- _Preserve_ the pointer to the queue after we release the work.

- Release the work _before_ executing the function, not after.

This simplifies some things: we no longer have to distinguish whether
the work is queued or running in the functions where we are trying to
modify it. The pointer has to be preserved even after the work is
released so that we can flush the workqueue after the work has been
released.

show more ...

Fix flush_delayed_work semantics: run it now if it was scheduled.

Reorder fields to get better space savings than bit fields.