Displaying 4 results from an estimated 4 matches for "virtio_config_change_".
Did you mean:
virtio_config_changed
2014 Oct 06
1
[PATCH 05/16] virtio: defer config changed notifications
...irtio_config_enable(struct virtio_device *dev)
> +{
> + spin_lock_irq(&dev->config_lock);
> + dev->config_enabled = true;
> + __virtio_config_changed(dev);
> + dev->config_changed = false;
> + spin_unlock_irq(&dev->config_lock);
> +}
> +
Maybe call these virtio_config_change_{dis,en}able()?
> static int virtio_dev_probe(struct device *_d)
> {
> int err, i;
2014 Oct 06
1
[PATCH 05/16] virtio: defer config changed notifications
...irtio_config_enable(struct virtio_device *dev)
> +{
> + spin_lock_irq(&dev->config_lock);
> + dev->config_enabled = true;
> + __virtio_config_changed(dev);
> + dev->config_changed = false;
> + spin_unlock_irq(&dev->config_lock);
> +}
> +
Maybe call these virtio_config_change_{dis,en}able()?
> static int virtio_dev_probe(struct device *_d)
> {
> int err, i;
2014 Oct 05
28
[PATCH 00/16] virtio: fix spec compliance issues
Rusty, I have a mind to send this patches for the next merge window.
Any input on this?
This fixes the following virtio spec compliance issues:
1. on restore, drivers use device before setting ACKNOWLEDGE and DRIVER bits
2. on probe, drivers aren't prepared to handle config interrupts
arriving before probe returns
3. on probe, drivers use device before DRIVER_OK it set
Note that 1 is a
2014 Oct 05
28
[PATCH 00/16] virtio: fix spec compliance issues
Rusty, I have a mind to send this patches for the next merge window.
Any input on this?
This fixes the following virtio spec compliance issues:
1. on restore, drivers use device before setting ACKNOWLEDGE and DRIVER bits
2. on probe, drivers aren't prepared to handle config interrupts
arriving before probe returns
3. on probe, drivers use device before DRIVER_OK it set
Note that 1 is a