When running under Xen as dom0 /dev/mcelog is being registered by Xen
instead of the normal mcelog driver. Avoid an error message being
issued by the mcelog driver in this case. Instead issue an informative
message that Xen has registered the device.
Signed-off-by: Juergen Gross
---
arch/x86/ker
On Tue, Jun 13, 2017 at 02:49:21PM +0200, Juergen Gross wrote:
> When running under Xen as dom0 /dev/mcelog is being registered by Xen
> instead of the normal mcelog driver. Avoid an error message being
> issued by the mcelog driver in this case. Instead issue an informative
> message that Xen has
On 13/06/17 15:02, Borislav Petkov wrote:
> On Tue, Jun 13, 2017 at 02:49:21PM +0200, Juergen Gross wrote:
>> When running under Xen as dom0 /dev/mcelog is being registered by Xen
>> instead of the normal mcelog driver. Avoid an error message being
>> issued by the mcelog driver in this case. Inste
On Tue, Jun 13, 2017 at 03:14:53PM +0200, Juergen Gross wrote:
> I'd rather avoid the pr_err() in the -EBUSY case. What about:
>
> if (err) {
> if (err == -EBUSY)
> pr_info("Unable to init device /dev/mcelog, already
> registered");
> else
> pr_err("Unable