Closed mclapinski closed 10 months ago
can we add a test to check that MEMBARRIER_CMD_REGISTER_GLOBAL_EXPEDITED is C/R-ed?
I can't check it the same way we check other membarrier commands because invoking MEMBARRIER_CMD_GLOBAL_EXPEDITED without MEMBARRIER_CMD_REGISTER_GLOBAL_EXPEDITED is valid.
I could try to check that the feature itself works (the membarrier is executed) but I don't know of a good way to write such a test.
I could check it using MEMBARRIER_CMD_GET_REGISTRATIONS but it would be duplicating the criu code so I'm not sure if it's valuable. LMK.
I could check it using MEMBARRIER_CMD_GET_REGISTRATIONS but it would be duplicating the criu code so I'm not sure if it's valuable. LMK.
@mclapinski I think it is valuable, we need to check that the criu part works as expected.
Patch coverage: 66.66%
and project coverage change: -0.19%
:warning:
Comparison is base (
82bfb67
) 70.67% compared to head (132871b
) 70.48%.:exclamation: Current head 132871b differs from pull request most recent head 6f131aa. Consider uploading reports for the commit 6f131aa to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@avagin Done. I think the CI failures are unrelated to my PR.
Merged. Thanks.
MEMBARRIER_CMD_GET_REGISTRATIONS can tell us whether or not the process used MEMBARRIER_CMD_REGISTER_GLOBAL_EXPEDITED unlike the old probing method.
Falls back to the old method when MEMBARRIER_CMD_GET_REGISTRATIONS is unavailable.