On 3/12/19 8:19 PM, Juergen Gross wrote: > On 12/03/2019 17:41, Hans van Kranenburg wrote: >> On 3/12/19 5:04 PM, Juergen Gross wrote: >>> On 11/03/2019 20:50, Hans van Kranenburg wrote: >>>> On 3/11/19 7:34 AM, Juergen Gross wrote: >>>>> >>>>> I'm not sure. Patch 3 of this series is basically already there (see >>>>> commit c6d4381220a0087ce19dbf6984d92c451bd6b364). So maybe all we need >>>>> is patch 4, which should really be easy to do? >>>>> >>>>> Hans, could you give it a try? You'd need to use a 4.20 kernel at least. >>>>> I can do the official patch posting in case you confirm it working. >>>> >>>> Ehm ok, well... This is interesting. >>>> >>>> I just built a 4.20.13 (without the patch), and I did it from the Debian >>>> kernel team repo, because then I just get all latest config options like >>>> I would get them in Debian. >>>> >>>> I rebooted the HP Z820 with it (with Xen 4.11) and I don't see any >>>> errors similar to the ones I pasted earlier. >>>> >>>> I haven't been running any domU on it yet (just installed it), but this >>>> is not what I expected. >>> >>> Well, commit c6d4381220a0087ce19dbf6984d92c451bd6b364 is part of a >>> rather large series making the dma interface cleaner and using it more >>> correctly where appropriate. Maybe your use case is covered by this >>> series already. >> >> It seems so. That's good, of course, but it also means that I cannot be >> of any use here any more to test the additional proposed change. ;] > > I don't think the change is needed any longer. > > Christoph's series was meant to fix stuff like that and it did that very > well.
Clear. Then for 4.19 in Debian the workaround is documented in here. And if someone from the kernel team is reading along... Please mark as solved when >= 4.20 is uploaded to Debian unstable? Hans