Fixing ACPI error reporting display
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest3 patches 9 repliesIn review
- v22 patches 7 repliesSuperseded
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | x86/APIC: include full string with error_interrupt() error messagesxen/ | +9 | 2 replies | |
| 2/3 | x86/APIC: modify error_interrupt() to output using single printk()xen/ | +7 | 3 replies | |
| 3/3 | x86/APIC: adjustments to error_interrupt() loopxen/ | +2 | 1 reply |
Reviews trailers per patch
All 3 patches have a Reviewed-by or Acked-by.
| Patch | Jan Beulich |
|---|---|
| 1/3 | A-b |
| 2/3 | A-b |
| 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 v3 0/3] Fixing ACPI error reporting display
This series has been seen previously. The issue is pretty simple, if ACPI errors occur there is a high probability they will occur on multiple cores at once. Since there is no locking for printk() there is a need to emit the entire error with a single printk().
I believe this is roughly where things left off. The loop adjustment had been requested to be broken into a separate step. I had also goofed when adjusting the handling and the string order had gotten reversed.
I'm unsure how best to make the printk() more maintainable. Yet more "%s" and entries[#] will be needed if additional bits get defined. I'm inclined to keep the string broken apart to hint as to how it matches the entry list. I'm okay with everything being fully concatenated if that is felt best.
Elliott Mitchell (3):
x86/APIC: include full string with error_interrupt() error messages x86/APIC: modify error_interrupt() to output using single printk() x86/APIC: adjustments to error_interrupt() loop
xen/arch/x86/apic.c | 32 +++++++++++++++++--------------- 1 file changed, 17 insertions(+), 15 deletions(-)
Signature · 1 line
2.30.2