Uploaded image for project: 'OASIS Virtual I/O Device (VIRTIO) TC'
  1. OASIS Virtual I/O Device (VIRTIO) TC
  2. VIRTIO-145

pci: configuration access capability rules are unclear

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: virtio 1.0 cs03
    • Fix Version/s: virtio 1.0 cs04
    • Labels:
      None
    • Environment:

      Michael S. Tsirkin <mst@redhat.com>

    • Proposal:
      Hide

      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.

      http://article.gmane.org/gmane.comp.emulators.virtio.devel/877

      Show
      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. http://article.gmane.org/gmane.comp.emulators.virtio.devel/877
    • Resolution:
      Show
      Accepted by electronic ballot: https://www.oasis-open.org/apps/org/workgroup/virtio/ballot.php?id=2865 Fixed in git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio/branches/v1.0@547 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652

      Description

      Specification merely says PCI config access capability
      aliases a device BAR. This seems to allow config access to
      legacy BAR (for transitional devices) but how should device
      interpret such an access?

        Attachments

          Activity

            People

            • Assignee:
              mstsirkin Michael S. Tsirkin
              Reporter:
              mstsirkin Michael S. Tsirkin
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: