mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-pci maillist <linux-pci@atrey.karlin.mff.cuni.cz>,
	Greg KH <greg@kroah.com>,
	Tom Long Nguyen <tom.l.nguyen@intel.com>
Subject: Re: [PATCH 2/6] PCI-Express AER implemetation
Date: Wed, 12 Jul 2006 09:41:47 +0800	[thread overview]
Message-ID: <1152668507.28493.180.camel@ymzhang-perf.sh.intel.com> (raw)
In-Reply-To: <1152668200.28493.178.camel@ymzhang-perf.sh.intel.com>

From: Zhang, Yanmin <yanmin.zhang@intel.com>

Patch 2 adds new defines of PCI-Express AER registers
and their bits into file include/linux/pci_regs.h.

Signed-off-by: Zhang Yanmin <yanmin.zhang@intel.com>

---

--- linux-2.6.17/include/linux/pci_regs.h	2006-06-22 16:26:31.000000000 +0800
+++ linux-2.6.17_aer/include/linux/pci_regs.h	2006-06-22 16:46:29.000000000 +0800
@@ -421,7 +421,23 @@
 #define  PCI_ERR_CAP_ECRC_CHKE	0x00000100	/* ECRC Check Enable */
 #define PCI_ERR_HEADER_LOG	28	/* Header Log Register (16 bytes) */
 #define PCI_ERR_ROOT_COMMAND	44	/* Root Error Command */
+/* Correctable Err Reporting Enable */
+#define PCI_ERR_ROOT_CMD_COR_EN		0x00000001
+/* Non-fatal Err Reporting Enable */
+#define PCI_ERR_ROOT_CMD_NONFATAL_EN	0x00000002
+/* Fatal Err Reporting Enable */
+#define PCI_ERR_ROOT_CMD_FATAL_EN	0x00000004
 #define PCI_ERR_ROOT_STATUS	48
+#define PCI_ERR_ROOT_COR_RCV		0x00000001	/* ERR_COR Received */
+/* Multi ERR_COR Received */
+#define PCI_ERR_ROOT_MULTI_COR_RCV	0x00000002
+/* ERR_FATAL/NONFATAL Recevied */
+#define PCI_ERR_ROOT_UNCOR_RCV		0x00000004
+/* Multi ERR_FATAL/NONFATAL Recevied */
+#define PCI_ERR_ROOT_MULTI_UNCOR_RCV	0x00000008
+#define PCI_ERR_ROOT_FIRST_FATAL	0x00000010	/* First Fatal */
+#define PCI_ERR_ROOT_NONFATAL_RCV	0x00000020	/* Non-Fatal Received */
+#define PCI_ERR_ROOT_FATAL_RCV		0x00000040	/* Fatal Received */
 #define PCI_ERR_ROOT_COR_SRC	52
 #define PCI_ERR_ROOT_SRC	54
 

  reply	other threads:[~2006-07-12  1:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12  1:36 [PATCH 1/6] " Zhang, Yanmin
2006-07-12  1:41 ` Zhang, Yanmin [this message]
2006-07-12  1:45   ` [PATCH 3/6] " Zhang, Yanmin
2006-07-12  1:53     ` [PATCH 4/6] " Zhang, Yanmin
2006-07-12  2:01       ` [PATCH 5/6] " Zhang, Yanmin
2006-07-12  2:08         ` [PATCH 6/6] " Zhang, Yanmin
2006-07-12  4:18 ` [PATCH 1/6] " Greg KH
2006-07-12  5:07   ` Zhang, Yanmin
2006-07-12  4:20 ` Greg KH
2006-07-12  5:08   ` Zhang, Yanmin
  -- strict thread matches above, loose matches on Subject: below --
2006-06-29  1:12 Zhang, Yanmin
2006-06-29  1:18 ` [PATCH 2/6] " Zhang, Yanmin

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=1152668507.28493.180.camel@ymzhang-perf.sh.intel.com \
    --to=yanmin_zhang@linux.intel.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=tom.l.nguyen@intel.com \
    /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

all inboxes | Powered by JetHome®