Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1693193 - vSMMUv3: Spurious config decoding errors when notifying IOVA invalidations
Summary: vSMMUv3: Spurious config decoding errors when notifying IOVA invalidations
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.0
Hardware: aarch64
OS: Linux
medium
medium
Target Milestone: rc
: 8.1
Assignee: Eric Auger
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1677408
TreeView+ depends on / blocked
 
Reported: 2019-03-27 10:18 UTC by Eric Auger
Modified: 2019-03-28 20:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Eric Auger 2019-03-27 10:18:55 UTC
In some guest PCIe configurations we can observe config decoding errors reported at early stage, such as:

invalid sid=512 (L1STD span=0)

This happens on guest IOVA invalidation forwarding. Those errors should be silenced in that specific case:

The IOVA invalidation is notified to all IOMMU Memory Regions (smmuv3_inv_notifiers_iova/smmuv3_notify_iova), ie. to all PCIe devices protected by the vSMMUv3. In smmuv3_notify_iova we attempt the decode the stream table entry associated to the device (smmuv3_decode_config) and it may happen that the STE is valid. In that case we should just ignore the issue as there is nothing to invalidate. We should be able to discriminate when the decode_config should not fail (in the translation path) and when it is allowed to fail.


Note You need to log in before you can comment on or make changes to this bug.