| Message ID | 20190611142821.3874-2-eric.auger@redhat.com |
|---|---|
| State | New |
| Headers | show |
| Series | ARM SMMUv3: Fix spurious notification errors and stall with vfio-pci | expand |
On Tue, 11 Jun 2019 at 15:29, Eric Auger <eric.auger@redhat.com> wrote: > > An IOVA/ASID invalidation is notified to all IOMMU Memory Regions > through smmuv3_inv_notifiers_iova/smmuv3_notify_iova. > > When the notification occurs it is possible that some of the > PCIe devices associated to the notified regions do not have a > valid stream table entry. In that case we output a LOG_GUEST_ERROR > message. > > invalid sid=<SID> (L1STD span=0) > "smmuv3_notify_iova error decoding the configuration for iommu mr=<MR> > > This is unfortunate as the user gets the impression that there > are some translation decoding errors whereas there are not. > > This patch adds a new field in SMMUEventInfo that tells whether > the detction of an invalid STE msut lead to an error report. > invalid_ste_allowed is set before doing the invalidations and > kept unset on actual translation. > > Signed-off-by: Eric Auger <eric.auger@redhat.com> > > --- > > I also experimented to pass Error handles to all the subfunctions > and handle the Error at top level but that's intricate to sort > out the various kinds of errors, whether they need to be logged, > and if so if they match LOG_GUEST_ERRoR mask or unimplemented > mask. So I think just passing this boolean has a lesser impact on > the code base. > --- > hw/arm/smmuv3-internal.h | 1 + > hw/arm/smmuv3.c | 11 +++++------ > 2 files changed, 6 insertions(+), 6 deletions(-) > > diff --git a/hw/arm/smmuv3-internal.h b/hw/arm/smmuv3-internal.h > index b160289cd1..d190181ef1 100644 > --- a/hw/arm/smmuv3-internal.h > +++ b/hw/arm/smmuv3-internal.h > @@ -381,6 +381,7 @@ typedef struct SMMUEventInfo { > uint32_t sid; > bool recorded; > bool record_trans_faults; > + bool inval_ste_allowed; > union { > struct { > uint32_t ssid; > diff --git a/hw/arm/smmuv3.c b/hw/arm/smmuv3.c > index fd8ec7860e..e2f07d2864 100644 > --- a/hw/arm/smmuv3.c > +++ b/hw/arm/smmuv3.c > @@ -404,7 +404,7 @@ static int smmu_find_ste(SMMUv3State *s, uint32_t sid, STE *ste, > > span = L1STD_SPAN(&l1std); > > - if (!span) { > + if (!span && !event->inval_ste_allowed) { > /* l2ptr is not valid */ > qemu_log_mask(LOG_GUEST_ERROR, > "invalid sid=%d (L1STD span=0)\n", sid); Why is this specific qemu_log_mask() the only one we need to suppress ? thanks -- PMM
Hi Peter, On 6/14/19 3:23 PM, Peter Maydell wrote: > On Tue, 11 Jun 2019 at 15:29, Eric Auger <eric.auger@redhat.com> wrote: >> >> An IOVA/ASID invalidation is notified to all IOMMU Memory Regions >> through smmuv3_inv_notifiers_iova/smmuv3_notify_iova. >> >> When the notification occurs it is possible that some of the >> PCIe devices associated to the notified regions do not have a >> valid stream table entry. In that case we output a LOG_GUEST_ERROR >> message. >> >> invalid sid=<SID> (L1STD span=0) >> "smmuv3_notify_iova error decoding the configuration for iommu mr=<MR> >> >> This is unfortunate as the user gets the impression that there >> are some translation decoding errors whereas there are not. >> >> This patch adds a new field in SMMUEventInfo that tells whether >> the detction of an invalid STE msut lead to an error report. >> invalid_ste_allowed is set before doing the invalidations and >> kept unset on actual translation. >> >> Signed-off-by: Eric Auger <eric.auger@redhat.com> >> >> --- >> >> I also experimented to pass Error handles to all the subfunctions >> and handle the Error at top level but that's intricate to sort >> out the various kinds of errors, whether they need to be logged, >> and if so if they match LOG_GUEST_ERRoR mask or unimplemented >> mask. So I think just passing this boolean has a lesser impact on >> the code base. >> --- >> hw/arm/smmuv3-internal.h | 1 + >> hw/arm/smmuv3.c | 11 +++++------ >> 2 files changed, 6 insertions(+), 6 deletions(-) >> >> diff --git a/hw/arm/smmuv3-internal.h b/hw/arm/smmuv3-internal.h >> index b160289cd1..d190181ef1 100644 >> --- a/hw/arm/smmuv3-internal.h >> +++ b/hw/arm/smmuv3-internal.h >> @@ -381,6 +381,7 @@ typedef struct SMMUEventInfo { >> uint32_t sid; >> bool recorded; >> bool record_trans_faults; >> + bool inval_ste_allowed; >> union { >> struct { >> uint32_t ssid; >> diff --git a/hw/arm/smmuv3.c b/hw/arm/smmuv3.c >> index fd8ec7860e..e2f07d2864 100644 >> --- a/hw/arm/smmuv3.c >> +++ b/hw/arm/smmuv3.c >> @@ -404,7 +404,7 @@ static int smmu_find_ste(SMMUv3State *s, uint32_t sid, STE *ste, >> >> span = L1STD_SPAN(&l1std); >> >> - if (!span) { >> + if (!span && !event->inval_ste_allowed) { >> /* l2ptr is not valid */ >> qemu_log_mask(LOG_GUEST_ERROR, >> "invalid sid=%d (L1STD span=0)\n", sid); > > Why is this specific qemu_log_mask() the only one we need > to suppress ? I focused on messages related to STE invalidity. This one corresponds to the 2-level stream table case where the top-level entry is invalid. In linear stream table case, the STE is fetched in smmu_get_ste(): this shouldn't fail as the STE table was allocated. Then its validity is checked in decode_ste() but up to now there is no tracing if the STE in not valid. I should revise this in the future though. Then obviously the config decoding is not over but I considered that if the STE is valid, the rest of the config should be valid as well. If we were to detect any error afterwards, those would deserve to be reported. Thanks Eric > > thanks > -- PMM >
diff --git a/hw/arm/smmuv3-internal.h b/hw/arm/smmuv3-internal.h index b160289cd1..d190181ef1 100644 --- a/hw/arm/smmuv3-internal.h +++ b/hw/arm/smmuv3-internal.h @@ -381,6 +381,7 @@ typedef struct SMMUEventInfo { uint32_t sid; bool recorded; bool record_trans_faults; + bool inval_ste_allowed; union { struct { uint32_t ssid; diff --git a/hw/arm/smmuv3.c b/hw/arm/smmuv3.c index fd8ec7860e..e2f07d2864 100644 --- a/hw/arm/smmuv3.c +++ b/hw/arm/smmuv3.c @@ -404,7 +404,7 @@ static int smmu_find_ste(SMMUv3State *s, uint32_t sid, STE *ste, span = L1STD_SPAN(&l1std); - if (!span) { + if (!span && !event->inval_ste_allowed) { /* l2ptr is not valid */ qemu_log_mask(LOG_GUEST_ERROR, "invalid sid=%d (L1STD span=0)\n", sid); @@ -602,7 +602,9 @@ static IOMMUTLBEntry smmuv3_translate(IOMMUMemoryRegion *mr, hwaddr addr, SMMUDevice *sdev = container_of(mr, SMMUDevice, iommu); SMMUv3State *s = sdev->smmu; uint32_t sid = smmu_get_sid(sdev); - SMMUEventInfo event = {.type = SMMU_EVT_NONE, .sid = sid}; + SMMUEventInfo event = {.type = SMMU_EVT_NONE, + .sid = sid, + .inval_ste_allowed = false}; SMMUPTWEventInfo ptw_info = {}; SMMUTranslationStatus status; SMMUState *bs = ARM_SMMU(s); @@ -795,16 +797,13 @@ static void smmuv3_notify_iova(IOMMUMemoryRegion *mr, dma_addr_t iova) { SMMUDevice *sdev = container_of(mr, SMMUDevice, iommu); - SMMUEventInfo event = {}; + SMMUEventInfo event = {.inval_ste_allowed = true}; SMMUTransTableInfo *tt; SMMUTransCfg *cfg; IOMMUTLBEntry entry; cfg = smmuv3_get_config(sdev, &event); if (!cfg) { - qemu_log_mask(LOG_GUEST_ERROR, - "%s error decoding the configuration for iommu mr=%s\n", - __func__, mr->parent_obj.name); return; }
An IOVA/ASID invalidation is notified to all IOMMU Memory Regions through smmuv3_inv_notifiers_iova/smmuv3_notify_iova. When the notification occurs it is possible that some of the PCIe devices associated to the notified regions do not have a valid stream table entry. In that case we output a LOG_GUEST_ERROR message. invalid sid=<SID> (L1STD span=0) "smmuv3_notify_iova error decoding the configuration for iommu mr=<MR> This is unfortunate as the user gets the impression that there are some translation decoding errors whereas there are not. This patch adds a new field in SMMUEventInfo that tells whether the detction of an invalid STE msut lead to an error report. invalid_ste_allowed is set before doing the invalidations and kept unset on actual translation. Signed-off-by: Eric Auger <eric.auger@redhat.com> --- I also experimented to pass Error handles to all the subfunctions and handle the Error at top level but that's intricate to sort out the various kinds of errors, whether they need to be logged, and if so if they match LOG_GUEST_ERRoR mask or unimplemented mask. So I think just passing this boolean has a lesser impact on the code base. --- hw/arm/smmuv3-internal.h | 1 + hw/arm/smmuv3.c | 11 +++++------ 2 files changed, 6 insertions(+), 6 deletions(-)