Commit d1c1dad8 authored by Cornelia Huck's avatar Cornelia Huck Committed by Michael S. Tsirkin
Browse files

virtio: document virtio_config_ops restrictions 



Some transports (e.g. virtio-ccw) implement virtio operations that
seem to be a simple read/write as something more involved that
cannot be done from an atomic context.

Give at least a hint about that.

Signed-off-by: default avatarCornelia Huck <cohuck@redhat.com>
Signed-off-by: default avatarMichael S. Tsirkin <mst@redhat.com>
parent b89a07c4

include/linux/virtio_config.h

+5 −0
Original line number Diff line number Diff line
@@ -12,6 +12,11 @@ struct irq_affinity; 


/**

 * virtio_config_ops - operations for configuring a virtio device

 * Note: Do not assume that a transport implements all of the operations

 *       getting/setting a value as a simple read/write! Generally speaking,

 *       any of @get/@set, @get_status/@set_status, or @get_features/

 *       @finalize_features are NOT safe to be called from an atomic

 *       context.

 * @get: read the value of a configuration field

 *	vdev: the virtio_device

 *	offset: the offset of the configuration field