xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] x86: restore (optional) forwarding of PCI SERR induced NMI to Dom0
Date: Mon, 21 Jan 2013 17:16:56 +0000	[thread overview]
Message-ID: <50FD7808.5000300@citrix.com> (raw)
In-Reply-To: <50FD818A02000078000B806A@nat28.tlf.novell.com>

On 21/01/13 16:57, Jan Beulich wrote:
>>>> On 21.01.13 at 17:16, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> On 21/01/13 16:11, Jan Beulich wrote:
>>> --- 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.
> Sure - did you look at the history of this (particularly the c/s
> mentioned in the description)?
>
>> Furthermore, the definition disagrees with the comment.
> In what way?
>
> Jan
>

Ah - I missed that being in public, and was thinking that you were
attempting to use (1UL<<1) to test against bit 7.  My mistake - sorry.

~Andrew

  reply	other threads:[~2013-01-21 17: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
2013-01-21 16:57   ` Jan Beulich
2013-01-21 17:16     ` Andrew Cooper [this message]
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=50FD7808.5000300@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).