From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: restore (optional) forwarding of PCI SERR induced NMI to Dom0
Date: Mon, 21 Jan 2013 16:16:15 +0000 [thread overview]
Message-ID: <50FD69CF.8030507@citrix.com> (raw)
In-Reply-To: <50FD76BD02000078000B7FBF@nat28.tlf.novell.com>
On 21/01/13 16:11, Jan Beulich wrote:
> c/s 22949:54fe1011f86b removed the forwarding of NMIs to Dom0 when they
> were caused by PCI SERR. NMI buttons as well as BMCs (like HP's iLO)
> may however want such events to be seen in Dom0 (e.g. to trigger a
> dump).
>
> Therefore restore most of the functionality which named c/s removed
> (adjusted for subsequent changes, and adjusting the public interface to
> use the modern term, retaining the old one for backwards
> compatibility).
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/arch/x86/traps.c
> +++ b/xen/arch/x86/traps.c
> @@ -3089,6 +3089,7 @@ static void nmi_mce_softirq(void)
> static void pci_serr_softirq(void)
> {
> printk("\n\nNMI - PCI system error (SERR)\n");
> + outb(inb(0x61) & 0x0b, 0x61); /* re-enable the PCI SERR error line. */
> }
>
> void async_exception_cleanup(struct vcpu *curr)
> @@ -3135,9 +3136,20 @@ static void pci_serr_error(struct cpu_us
> {
> outb((inb(0x61) & 0x0f) | 0x04, 0x61); /* clear-and-disable the PCI SERR error line. */
>
> - /* Would like to print a diagnostic here but can't call printk()
> - from NMI context -- raise a softirq instead. */
> - raise_softirq(PCI_SERR_SOFTIRQ);
> + switch ( opt_nmi[0] )
> + {
> + case 'd': /* 'dom0' */
> + nmi_dom0_report(_XEN_NMIREASON_pci_serr);
> + case 'i': /* 'ignore' */
> + /* Would like to print a diagnostic here but can't call printk()
> + from NMI context -- raise a softirq instead. */
> + raise_softirq(PCI_SERR_SOFTIRQ);
> + break;
> + default: /* 'fatal' */
> + console_force_unlock();
> + printk("\n\nNMI - PCI system error (SERR)\n");
> + fatal_trap(TRAP_nmi, regs);
> + }
> }
>
> static void io_check_error(struct cpu_user_regs *regs)
> --- a/xen/include/public/nmi.h
> +++ b/xen/include/public/nmi.h
> @@ -36,9 +36,14 @@
> /* I/O-check error reported via ISA port 0x61, bit 6. */
> #define _XEN_NMIREASON_io_error 0
> #define XEN_NMIREASON_io_error (1UL << _XEN_NMIREASON_io_error)
> + /* PCI SERR reported via ISA port 0x61, bit 7. */
> +#define _XEN_NMIREASON_pci_serr 1
> +#define XEN_NMIREASON_pci_serr (1UL << _XEN_NMIREASON_pci_serr)
> +#if __XEN_INTERFACE_VERSION__ < 0x00040300 /* legacy alias of the above */
> /* Parity error reported via ISA port 0x61, bit 7. */
These seem wrong. Both SERR and Parity error have the same comment and
definition.
Furthermore, the definition disagrees with the comment.
~Andrew
> #define _XEN_NMIREASON_parity_error 1
> #define XEN_NMIREASON_parity_error (1UL << _XEN_NMIREASON_parity_error)
> +#endif
> /* Unknown hardware-generated NMI. */
> #define _XEN_NMIREASON_unknown 2
> #define XEN_NMIREASON_unknown (1UL << _XEN_NMIREASON_unknown)
>
>
>
next prev parent reply other threads:[~2013-01-21 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 16:11 [PATCH] x86: restore (optional) forwarding of PCI SERR induced NMI to Dom0 Jan Beulich
2013-01-21 16:16 ` Andrew Cooper [this message]
2013-01-21 16:57 ` Jan Beulich
2013-01-21 17:16 ` Andrew Cooper
2013-01-21 16:20 ` Stefano Stabellini
2013-01-21 16:28 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50FD69CF.8030507@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.