RFC x86: Mad WARN() hackery
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest8 patches 12 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | x86: Provide assembly __bug_table helpersarch/ | +24 | 0 replies | |
| 2/8 | bug: Add BUGFLAG_FORMAT infrastructureinclude/ lib/ | +28 | 0 replies | |
| 3/8 | bug: Clean up CONFIG_GENERIC_BUG_RELATIVE_POINTERSinclude/ | +8 | 0 replies | |
| 4/8 | bug: Allow architectures to provide __WARN_printf()include/ | +13 | 0 replies | |
| 5/8 | x86_64/bug: Add BUG_FORMAT basicsarch/ | +18 | 0 replies | |
| 6/8 | x86_64/bug: Implement __WARN_printf()arch/ arch/ | +225 | 12 replies | |
| 7/8 | x86/bug: Implement WARN_ONCE()arch/ include/ | +30 | 0 replies | |
| 8/8 | x86: Clean up default rethunk warningarch/ arch/ arch/ +1 more | +17 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC 0/8] x86: Mad WARN() hackery
Hi,
I've been annoyed at how WARN() works for quite some time, and Alessandro has been trying to make it even worse.
This is an attempt at making WARN() generate less crap for the most common cases. It is somewhat magical, but appears to be working for the simple cases I've tried. Specifically, it moves the __warn_printf() into the exception for the case of 3 or less arguments.
This would hopefully allow Allesandro to put the kunit hackery in report_bug() and not spread it around all the WARN() sites like he does now.