diff options
| author | pbonzini <pbonzini@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2014-06-17 13:12:30 +0000 |
|---|---|---|
| committer | pbonzini <pbonzini@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652> | 2014-06-17 13:12:30 +0000 |
| commit | a2503484f0579b0b6547c36207c0381a7eee2a4d (patch) | |
| tree | 6d556b682b5eca7978389da5a540262fa5eae606 | |
| parent | 65853394e08c2f97ae68594496d0f187aeb65590 (diff) | |
content.tex: VIRTIO-106: mention possibility of failing TMFs
This completes the review of virtio-scsi based on observations
from Google.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@384 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
| -rw-r--r-- | content.tex | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/content.tex b/content.tex index 56f58fa..e81636c 100644 --- a/content.tex +++ b/content.tex @@ -4811,9 +4811,9 @@ struct virtio_scsi_ctrl_tmf Similarly, the device MUST complete the selected commands (possibly with a VIRTIO_SCSI_S_ABORTED response code) upon receiving an "abort task" or "abort task set" TMF. Such effects MUST take place before - the TMF itself is completed, and the device MUST use memory barriers - appropriately in order to ensure that the driver sees these writes - in the correct order. + the TMF itself is successfully completed, and the device MUST use + memory barriers appropriately in order to ensure that the driver sees + these writes in the correct order. \item Asynchronous notification query. \begin{lstlisting} |