On 2013/10/18 20:37, Naveen N. Rao wrote:
> On 10/18/2013 01:53 PM, Chen, Gong wrote:
>> This H/W error log driver (a.k.a eMCA driver) is implemented based on
>> http://www.intel.com/content/www/us/en/architecture-and-technology/enhanced-mca-logging-xeon-paper.html
>>
>> After errors are captured, more valuable information can be
>> got via this new enhanced H/W error log driver.
>>
>> v3 -> v2: fix a MACRO definition error and some cleanup
>> v2 -> v1: eliminate spin_lock & minor fixes suggested by Boris
>>
>> Signed-off-by: Chen, Gong <gong.c...@linux.intel.com>
>> ---
>> arch/x86/include/asm/mce.h | 5 +
>> arch/x86/kernel/cpu/mcheck/mce.c | 20 +++
>> drivers/acpi/Kconfig | 20 +++
>> drivers/acpi/Makefile | 2 +
[...]
>> +}
>> +EXPORT_SYMBOL_GPL(unregister_elog_handler);
>> +
>> /*
>> * Poll for corrected events or events that happened before reset.
>> * Those are just logged through /dev/mcelog.
>> @@ -624,6 +641,9 @@ void machine_check_poll(enum mcp_flags flags,
>> mce_banks_t *b)
>> (m.status & (mca_cfg.ser ? MCI_STATUS_S : MCI_STATUS_UC)))
>> continue;
>>
>> + if (mce_ext_err_print)
>> + mce_ext_err_print(NULL, m.extcpu, i);
>> +
>
> Can we use the notifier chain we already have: mce_register_decode_chain()?
> EDAC uses this and I'm wondering if it is a good fit here. As an added bonus,
> it seems to honor dont_log_ce option as well.
Hi everyone,
I have a question here, is it safe when we use printk in MCE context?
The call graph is like this,
do_machine_check
-> mce_log
-> atomic_notifier_call_chain(&x86_mce_decoder_chain ...)
-> ...
-> extlog_print
-> print_extlog_rcd
-> __print_extlog_rcd
-> printk
There's a logbuf_lock in printk. If logbuf_lock is held by other cpu,
it'll lead to an infinity spin here. Isn't it?
--
Thanks,
XiuQi
>
>> mce_read_aux(&m, i);
>>
>> if (!(flags & MCP_TIMESTAMP))
>> diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
>> index 22327e6..c67ec61 100644
>> --- a/drivers/acpi/Kconfig
>> +++ b/drivers/acpi/Kconfig
>> @@ -372,4 +372,24 @@ config ACPI_BGRT
>>
>> source "drivers/acpi/apei/Kconfig"
>>
>> +config ACPI_EXTLOG
>> + tristate "Extended Error Log support"
>> + depends on X86_MCE
...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
