s390: Enable CONTEXT_ANALYSIS for cio and virtio
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 9 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | s390/vfio_ccw: Add __must_hold() attribute to vfio_ccw_sch_quiesce()drivers/ drivers/ | +3 | 7 replies | |
| 2/3 | s390/cio: Enable CONTEXT_ANALYSISdrivers/ | +2 | 0 replies | |
| 3/3 | s390/virtio: Enable CONTEXT_ANALYSISdrivers/ | +2 | 1 reply |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Matthew Rosato | Christian Borntraeger |
|---|---|---|
| 1/3 | R-b | A-b |
| 2/3 | ||
| 3/3 | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] s390: Enable CONTEXT_ANALYSIS for cio and virtio
Enable CONTEXT_ANALYSYS for cio and virtio.
Static code checking for acquiring and releasing locks used to be done with sparse. That was removed with [1] and replaced with a clang based approach [2]. The new approach requires that each subsystem needs to be explicitly enabled for checking.
Do that for cio and virtio. Add a __must_hold() attribute to vfio_ccw_sch_quiesce() to address the only valid warning.
Then enable CONTEXT_ANALYSIS for both cio and virtio.
Christian, Claudio, Janosch, I think it would make most sense if this goes via kvms390.
Thanks,
Heiko
[1] 5b63d0ae94cc ("compiler-context-analysis: Remove Sparse support")
[2] 3269701cb256 ("compiler-context-analysis: Add infrastructure for Context Analysis with Clang")
Heiko Carstens (3):
s390/vfio_ccw: Add __must_hold() attribute to vfio_ccw_sch_quiesce() s390/cio: Enable CONTEXT_ANALYSIS
s390/virtio: Enable CONTEXT_ANALYSIS
drivers/s390/cio/Makefile | 2 ++ drivers/s390/cio/vfio_ccw_drv.c | 1 + drivers/s390/cio/vfio_ccw_private.h | 3 ++- drivers/s390/virtio/Makefile | 2 ++ 4 files changed, 7 insertions(+), 1 deletion(-)
Signature · 1 line
2.53.0