Page MenuHomeFreeBSD

hwpmc: don't validate capabilities in allocation method
ClosedPublic

Authored by mhorne on Aug 2 2021, 9:09 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Dec 5, 3:37 PM
Unknown Object (File)
Wed, Dec 4, 6:48 AM
Unknown Object (File)
Fri, Nov 29, 5:33 AM
Unknown Object (File)
Wed, Nov 27, 10:53 AM
Unknown Object (File)
Nov 17 2024, 3:51 AM
Unknown Object (File)
Oct 27 2024, 12:42 PM
Unknown Object (File)
Oct 26 2024, 1:11 AM
Unknown Object (File)
Oct 24 2024, 10:07 PM
Subscribers

Details

Summary

These checks were inconsistently applied across the various hwpmc
classes. The condition is already checked by the generic code in
hwpmc_mod.c, so remove them.

Test Plan

Tinderboxed.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

mhorne requested review of this revision.Aug 2 2021, 9:09 PM

Some existing cases returned EPERM for the != caps cases?

Some existing cases returned EPERM for the != caps cases?

Yes exactly.

Although, I just noticed the generic allocation code in hwpmc_mod.c checks the capabilities before any of these class-specific checks, so they are more or less useless. I will update this review to just remove them altogether.

The relevant line is here: https://cgit.freebsd.org/src/tree/sys/dev/hwpmc/hwpmc_mod.c#n3935

Switch to just removing the existing redundant capability checks.

mhorne retitled this revision from hwpmc: consistently validate capabilities in pcd_allocate_pmc() to hwpmc: don't validate capabilities in allocation method.Aug 11 2021, 4:43 PM
mhorne edited the summary of this revision. (Show Details)
This revision was not accepted when it landed; it landed in state Needs Review.Aug 30 2021, 7:16 PM
This revision was automatically updated to reflect the committed changes.