From cbeb3b681713eae1d736e5cc84672c6702989d94 Mon Sep 17 00:00:00 2001
From: mstsirkin <mstsirkin@0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652>
Date: Wed, 21 Oct 2015 14:21:41 +0000
Subject: cl: document resolution for VIRTIO-145.

pci: clarify configuration access capability rules

Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/branches/v1.0@550 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652
---
 cl-os.tex | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

(limited to 'cl-os.tex')

diff --git a/cl-os.tex b/cl-os.tex
index 6befac3..34862e5 100644
--- a/cl-os.tex
+++ b/cl-os.tex
@@ -50,3 +50,19 @@ See \ref{sec:Device Types / Block Device},
 \ref{sec:Conformance / Device Conformance / Block Device Conformance}.
 } \\
 \hline
+546 & 18 Oct 2015 & Michael S. Tsirkin & {pci: clarify configuration access capability rules
+
+The point of the configuration access capability is to enable
+access to other capabilities.  The intent never was to allow
+writes to a random place within device BARs.
+Limiting drivers simplifies devices - and devices can always
+add another capability if drivers ever want to access
+some other range.
+
+This resolves VIRTIO-145.
+
+See \ref{drivernormative:Virtio Transport Options / Virtio Over
+PCI Bus / PCI Device Layout / PCI configuration access
+capability}.
+} \\
+\hline
-- 
cgit v1.2.3

