[PATCH 09/32] drm/radeon: use system_wq instead of dev_priv->wq

On Tue, 2011-01-04 at 19:21 -0500, Alex Deucher wrote: > On Mon, Jan 3, 2011 at 8:49 AM, Tejun Heo wrote: > > With cmwq, there's no reason for radeon to use a dedicated workqueue. > > Drop dev_priv->wq and use system_wq instead. > > > > Because radeon_driver_irq_uninstall_kms() may be called from

Re: [PATCH 09/32] drm/radeon: use system_wq instead of dev_priv->wq

On Tue, 2011-01-04 at 19:21 -0500, Alex Deucher wrote: > On Mon, Jan 3, 2011 at 8:49 AM, Tejun Heo wrote: > > With cmwq, there's no reason for radeon to use a dedicated workqueue. > > Drop dev_priv->wq and use system_wq instead. > > > > Because radeon_driver_irq_uninstall_kms() may be called from

[PATCH 09/32] drm/radeon: use system_wq instead of dev_priv->wq

On Mon, Jan 3, 2011 at 8:49 AM, Tejun Heo wrote: > With cmwq, there's no reason for radeon to use a dedicated workqueue. > Drop dev_priv->wq and use system_wq instead. > > Because radeon_driver_irq_uninstall_kms() may be called from > unsleepable context, the work items can't be flushed from there

Re: [PATCH 09/32] drm/radeon: use system_wq instead of dev_priv->wq

On Mon, Jan 3, 2011 at 8:49 AM, Tejun Heo wrote: > With cmwq, there's no reason for radeon to use a dedicated workqueue. > Drop dev_priv->wq and use system_wq instead. > > Because radeon_driver_irq_uninstall_kms() may be called from > unsleepable context, the work items can't be flushed from there

[PATCH 09/32] drm/radeon: use system_wq instead of dev_priv->wq

With cmwq, there's no reason for radeon to use a dedicated workqueue. Drop dev_priv->wq and use system_wq instead. Because radeon_driver_irq_uninstall_kms() may be called from unsleepable context, the work items can't be flushed from there. Instead, init and flush from radeon_irq_kms_init/fini().

[PATCH 09/32] drm/radeon: use system_wq instead of dev_priv->wq

With cmwq, there's no reason for radeon to use a dedicated workqueue. Drop dev_priv->wq and use system_wq instead. Because radeon_driver_irq_uninstall_kms() may be called from unsleepable context, the work items can't be flushed from there. Instead, init and flush from radeon_irq_kms_init/fini().