RFC Clean up x86 CPU feature setup
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | x86: use defined names for all CPU feature flagsarch/ arch/ arch/ +3 more | +10 | 3 replies | |
| 2/3 | x86: new API for modifying CPU feature flagsinclude/ | +17 | 0 replies | |
| 3/3 | x86: use the x86 CPU feature APIarch/ arch/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/3] Clean up x86 CPU feature setup
x86 CPU feature flag setup has become impossible to debug. Every user just does set_bit()/clear_bit() or writes the entire set to change the flags, so there's no way to trace how they're being set.
This patchset creates an API and debug messages for tracking how the flags get set. It's not nearly done, but I want to know whether or not to continue.