mmu_notifiers follow ups
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | xen/gntdev: fix up blockable calls to mn_invl_range_startdrivers/ | +15 | 2 replies | |
| 2/3 | mm, mmu_notifier: be explicit about range invalition non-blocking modeinclude/ | +3 | 1 reply | |
| 3/3 | Revert "mm, mmu_notifier: annotate mmu notifiers with blockable invalidate callbacks"drivers/ drivers/ drivers/ +4 more | +0 | 0 replies |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Jerome Glisse | Juergen Gross |
|---|---|---|
| 1/3 | R-b | |
| 2/3 | R-b | |
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] mmu_notifiers follow ups
Hi Andrew,
Tetsuo has noticed some fallouts from 93065ac753e4 ("mm, oom:
distinguish blockable mode for mmu notifiers"). One of them has been fixed and picked up by AMD/DRM maintainer [1]. XEN issue is fixed by patch 1. I have also clarified expectations about blockable semantic of invalidate_range_end. Finally the last patch removes MMU_INVALIDATE_DOES_NOT_BLOCK which is no longer used nor needed.