From 57110bc3ae9e9a7bcf8fb538d33ce5f3a88d61f0 Mon Sep 17 00:00:00 2001 From: "cornelia.huck" Date: Mon, 4 Nov 2013 15:14:46 +0000 Subject: ccw: Improve indicator wording. Be clearer about traditional vs. adapter interrupts and virtqueue vs. configuration indicators. Signed-off-by: Cornelia Huck git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@84 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652 --- virtio-v1.0-wd01-part1-specification.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt index 18cb6b6..8a649f2 100644 --- a/virtio-v1.0-wd01-part1-specification.txt +++ b/virtio-v1.0-wd01-part1-specification.txt @@ -1915,11 +1915,13 @@ version, and keep a generation count internally whenever it changes. In order to set up the indicator bits for host->guest notification, the driver uses different channel commands depending on whether it wishes to use traditional I/O interrupts tied to a subchannel or -adapter I/O interrupts. For any given device, the two mechanisms -are mutually exclusive. +adapter I/O interrupts for virtqueue notifications. For any given +device, the two mechanisms are mutually exclusive. -For the configuration change indicators, the same mechanism is used -in both cases. +For the configuration change indicators, only a mechanism using +traditional I/O interrupts is provided, regardless of whether +traditional or adapter I/O interrupts are used for virtqueue +notifications. 2.3.3.2.5.1. Setting Up Classic Queue Indicators ------------------------------------------------ -- cgit v1.2.3