public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* RE: [PATCH 5/6] PCI Express Advanced Error Reporting Driver
@ 2005-03-15 18:33 Nguyen, Tom L
  2005-03-12  0:10 ` [PATCH 0/6] " long
  0 siblings, 1 reply; 12+ messages in thread
From: Nguyen, Tom L @ 2005-03-15 18:33 UTC (permalink / raw)
  To: Greg KH, long; +Cc: linux-kernel, linux-pci

Friday, March 11, 2005 11:30 PM Greg KH wrote:
>> +
>> +LIST_HEAD(rc_list);			/* Define Root Complex List */
>>
>Static?

The rc_list is not static. Thanks for pointing it out. Will make it
static. 

Thanks,
Long

^ permalink raw reply	[flat|nested] 12+ messages in thread
* RE: [PATCH 0/6] PCI Express Advanced Error Reporting Driver
@ 2005-03-18 18:44 Nguyen, Tom L
  0 siblings, 0 replies; 12+ messages in thread
From: Nguyen, Tom L @ 2005-03-18 18:44 UTC (permalink / raw)
  To: Grant Grundler; +Cc: Greg KH, linux-kernel, linux-pci, Nguyen, Tom L

On Friday, March 18, 2005 10:26 AM Grant Grundler wrote:
>> He was referring to an unpublished draft "Error Reporting ECN".
>> You'll have to talk to Intel's PCI-SIG representative to get a copy.
>
>Good News: the "Error Reporting ECN" is now posted on the PCISIG
website.
>
>Tom, please review and see if/how that changes your implementation.

Agree. Thanks for the update.

Thanks,
Long

^ permalink raw reply	[flat|nested] 12+ messages in thread
* RE: [PATCH 0/6] PCI Express Advanced Error Reporting Driver
@ 2005-03-15 22:41 Nguyen, Tom L
  0 siblings, 0 replies; 12+ messages in thread
From: Nguyen, Tom L @ 2005-03-15 22:41 UTC (permalink / raw)
  To: Grant Grundler; +Cc: Greg KH, linux-kernel, linux-pci, Nguyen, Tom L

On Tuesday, March 15, 2005 2:38 PM Grant Grundler wrote:
>> >A co-worker made the following observation (I'm paraphrasing):
>> >	...this proposal does not deal with the Error Reporting ECN.
>> >	For example, they do not show the advisory non-fatal bit in
>> >	the correctable error status register.
>> 
>> Does he refer to the ECN update on the Received Error Bit[0] of the
>> Correctable Error Status Register and on the Training Error Bit[0] of
>> the Uncorrectable Error Status Register? If not, please clarify his
>> comments for us.

>Yes - I believe so.

Great! I will make changes to reflect this update. Thanks for pointing
it out.

Thanks,
Long

^ permalink raw reply	[flat|nested] 12+ messages in thread
* RE: [PATCH 0/6] PCI Express Advanced Error Reporting Driver
@ 2005-03-15 21:54 Nguyen, Tom L
  2005-03-15 22:38 ` Grant Grundler
  0 siblings, 1 reply; 12+ messages in thread
From: Nguyen, Tom L @ 2005-03-15 21:54 UTC (permalink / raw)
  To: Grant Grundler; +Cc: Greg KH, linux-kernel, linux-pci, Nguyen, Tom L

On Tuesday, March 15, 2005 12:12 PM Grant Grundler wrote:
>Tom,
>A co-worker made the following observation (I'm paraphrasing):
>	...this proposal does not deal with the Error Reporting ECN.
>	For example, they do not show the advisory non-fatal bit in
>	the correctable error status register.

Does he refer to the ECN update on the Received Error Bit[0] of the
Correctable Error Status Register and on the Training Error Bit[0] of
the Uncorrectable Error Status Register? If not, please clarify his
comments for us.

Thanks,
Long

^ permalink raw reply	[flat|nested] 12+ messages in thread
* RE: [PATCH 0/6] PCI Express Advanced Error Reporting Driver
@ 2005-03-14 18:34 Nguyen, Tom L
  0 siblings, 0 replies; 12+ messages in thread
From: Nguyen, Tom L @ 2005-03-14 18:34 UTC (permalink / raw)
  To: Greg KH, long; +Cc: linux-kernel, linux-pci, Nguyen, Tom L

On Friday, March 11, 2005 11:21 PM Greg KH wrote:
>> 
>> -	Report the errors to user.
>>
>This is done through the syslog, right?  Is that acceptable?

Reporting the errors to user can be written automatically to
/var/log/messages or be manually consumed through the syslog. I am not
sure whether it is acceptable or not, but I like your below suggestion. 

>It looks like you are logging a lot of stuff, all without a kernel log
>level, which is going to really mess up syslog parsers.
>
>Have you thought about just providing userspace with access to the
error
>message, in binary form, from a sysfs file, and causing a kevent to
wake
>userspace up to know to read from the file?  That way all of the
parsing
>of the error log can be done in userspace, and there is no formatting
of
>the messages from within the kernel.

Again, I like this suggestion.

Thanks,
Long

^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2005-03-18 18:44 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-03-15 18:33 [PATCH 5/6] PCI Express Advanced Error Reporting Driver Nguyen, Tom L
2005-03-12  0:10 ` [PATCH 0/6] " long
2005-03-12  7:20   ` Greg KH
2005-03-15 20:11   ` Grant Grundler
2005-03-16  2:12     ` Grant Grundler
2005-03-16  2:24       ` Greg KH
2005-03-18 18:26       ` Grant Grundler
  -- strict thread matches above, loose matches on Subject: below --
2005-03-18 18:44 Nguyen, Tom L
2005-03-15 22:41 Nguyen, Tom L
2005-03-15 21:54 Nguyen, Tom L
2005-03-15 22:38 ` Grant Grundler
2005-03-14 18:34 Nguyen, Tom L

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox