[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [PATCH] virtio-ccw: Switch to device/driver language.
Switch the parts of the virtio-ccw specification that did not already to device/driver instead of guest/host. For more general discussions, host/guest is kept (like when talking about guest<->host notifications in general). This should make things more consistent. Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com> --- virtio-v1.0-wd01-part1-specification.txt | 38 +++++++++++++++--------------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt index ba3ecae..d7f956d 100644 --- a/virtio-v1.0-wd01-part1-specification.txt +++ b/virtio-v1.0-wd01-part1-specification.txt @@ -1952,7 +1952,7 @@ implies that the device must reject any command not valid for revision 2.3.3.2.2. Configuring a Virtqueue ---------------------------------- -CCW_CMD_READ_VQ_CONF is issued by the guest to obtain information +CCW_CMD_READ_VQ_CONF is issued by the driver to obtain information about a queue. It uses the following structure for communicating: struct vq_config_block { @@ -1963,8 +1963,8 @@ about a queue. It uses the following structure for communicating: The requested number of buffers for queue index is returned in max_num. -Afterwards, CCW_CMD_SET_VQ is issued by the guest to inform the -host about the location used for its queue. The transmitted +Afterwards, CCW_CMD_SET_VQ is issued by the driver to inform the +device about the location used for its queue. The transmitted structure is struct vq_info_block { @@ -2020,7 +2020,7 @@ The calculation for total size is as follows: 2.3.3.2.3. Communicating Status Information ------------------------------------------- -The guest can change the status of a device via the +The driver can change the status of a device via the CCW_CMD_WRITE_STATUS command, which transmits an 8 bit status value. @@ -2043,11 +2043,11 @@ features are the 32 bits of features currently accessed, while index describes which of the feature bit values is to be accessed. -The guest may obtain the host's device feature set via the -CCW_CMD_READ_FEAT command. The host stores the features at index +The guest may obtain the device's device feature set via the +CCW_CMD_READ_FEAT command. The device stores the features at index to features. -For communicating its device features to the host, the guest may +For communicating its supported features to the device, the driver may use the CCW_CMD_WRITE_FEAT command, denoting a features/index combination. @@ -2057,16 +2057,16 @@ combination. The device's configuration space is located in host memory. It is the same size as the standard PCI configuration space. -To obtain information from the configuration space, the guest may -use CCW_CMD_READ_CONF, specifying the guest memory for the host +To obtain information from the configuration space, the driver may +use CCW_CMD_READ_CONF, specifying the guest memory for the device to write to. -For changing configuration information, the guest may use -CCW_CMD_WRITE_CONF, specifying the guest memory for the host to +For changing configuration information, the driver may use +CCW_CMD_WRITE_CONF, specifying the guest memory for the device to read from. In both cases, the complete configuration space is transmitted. This -allows the guest to compare the new configuration space with the old +allows the driver to compare the new configuration space with the old version, and keep a generation count internally whenever it changes. 2.3.3.2.6. Setting Up Indicators @@ -2090,7 +2090,7 @@ Indicators for notification via classic I/O interrupts are contained in a 64 bit value per virtio-ccw proxy device. To communicate the location of the indicator bits for host->guest -notification, the guest uses the CCW_CMD_SET_IND command, +notification, the driver uses the CCW_CMD_SET_IND command, pointing to a location containing the guest address of the indicators in a 64 bit value. @@ -2170,12 +2170,12 @@ If the driver used the CCW_CMD_SET_IND command to set up queue indicators, the device will use classic I/O interrupts for host->guest notification about virtqueue activity. -For notifying the guest of virtqueue buffers, the host sets the +For notifying the driver of virtqueue buffers, the device sets the corresponding bit in the guest-provided indicators. If an -interrupt is not already pending for the subchannel, the host +interrupt is not already pending for the subchannel, the device generates an unsolicited I/O interrupt. -If the host wants to notify the guest about configuration +If the device wants to notify the driver about configuration changes, it sets bit 0 in the configuration indicators and generates an unsolicited I/O interrupt, if needed. This also applies if adapter I/O interrupts are used for queue notifications. @@ -2187,7 +2187,7 @@ If the driver used the CCW_CMD_SET_IND_ADAPTER command to set up queue indicators, the device will use adapter I/O interrupts for host->guest notification about virtqueue activity. -For notifying the guest of virtqueue buffers, the host sets the +For notifying the driver of virtqueue buffers, the device sets the bit in the guest-provided indicator area at the corresponding offset. The guest-provided summary indicator is also set. An adapter I/O interrupt for the corresponding interruption subclass is generated. @@ -2205,7 +2205,7 @@ host->guest notification will always be done via classic I/O interrupts. 2.3.3.3.2. Guest->Host Notification ----------------------------------- -For notifying the host of virtqueue buffers, the guest +For notifying the device of virtqueue buffers, the driver unfortunately can't use a channel command (the asynchronous characteristics of channel I/O interact badly with the host block I/O backend). Instead, it uses a diagnose 0x500 call with subcode @@ -2242,7 +2242,7 @@ used. 2.3.3.3.4. Resetting Devices ---------------------------- -In order to reset a device, a guest may send the +In order to reset a device, a driver may send the CCW_CMD_VDEV_RESET command. -- 1.7.9.5
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]