On Fri, May 20, 2022 at 02:46:39PM +0200, Jan Beulich wrote: > On 20.05.2022 14:36, Roger Pau Monné wrote: > > On Thu, Apr 21, 2022 at 03:21:08PM +0200, Roger Pau Monne wrote: > >> Hello, > >> > >> Following series attempts to solve the issue with IO-APIC edge triggered > >> interrupts seeing an inconsistent RTE or IRTE when injected while being > >> migrated. > >> > >> It's currently RFC because some patches have post commit message notes, > >> and because I'm not sure if patch 1 is really needed. I originally had > >> the idea of suggesting to only backport patch 1 in order to fix the > >> issue in older releases, while leaving the more complex (and thus > >> error prone) IOMMU changes in unstable. Note however that patch 1 is > >> just a workaround to prevent interrupts seeing inconsistent entries > >> while being updated, masking the entry just makes the warning go away, > >> but the interrupt will be lost. > > > > Ping? > > Sorry, the usual thing with RFCs: They take lower priority than other > work items. This series is certainly the first of the several pending > RFC series which I mean to get to, but it's hard to predict when this > would be.
No problem, I don't think it's a super urgent issue: we have always handled interrupts this way and so far got no noticeable issues (apart from the log messages reported on the console). There's a non-trivial amount of IOMMU code changes, so maybe the IOMMU maintainers could take a stab at those as a start? Thanks, Roger.
