Re: [PATCHv4 1/2] iommu/vt-d: Ratelimit each dmar fault printing

2018-05-03 Thread Dmitry Safonov
On Thu, 2018-05-03 at 14:40 +0200, Joerg Roedel wrote: > On Wed, May 02, 2018 at 03:22:24AM +0100, Dmitry Safonov wrote: > > Hi Joerg, > > > > is there anything I may do about those two patches? > > In 2/2 I've limited loop cnt as discussed in v3. > > This one solves softlockup for us, might be us

Re: [PATCHv4 1/2] iommu/vt-d: Ratelimit each dmar fault printing

2018-05-03 Thread Joerg Roedel
On Wed, May 02, 2018 at 03:22:24AM +0100, Dmitry Safonov wrote: > Hi Joerg, > > is there anything I may do about those two patches? > In 2/2 I've limited loop cnt as discussed in v3. > This one solves softlockup for us, might be useful. Applied the first patch, thanks. Please re-work the second o

Re: [PATCHv4 1/2] iommu/vt-d: Ratelimit each dmar fault printing

2018-05-01 Thread Dmitry Safonov
Hi Joerg, is there anything I may do about those two patches? In 2/2 I've limited loop cnt as discussed in v3. This one solves softlockup for us, might be useful. On Sat, 2018-03-31 at 01:33 +0100, Dmitry Safonov wrote: > There is a ratelimit for printing, but it's incremented each time the > cpu

[PATCHv4 1/2] iommu/vt-d: Ratelimit each dmar fault printing

2018-03-30 Thread Dmitry Safonov
There is a ratelimit for printing, but it's incremented each time the cpu recives dmar fault interrupt. While one interrupt may signal about *many* faults. So, measuring the impact it turns out that reading/clearing one fault takes < 1 usec, and printing info about the fault takes ~170 msec. Havin