All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: long <tlnguyen@snoqualmie.dp.intel.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	tom.l.nguyen@intel.com
Subject: Re: [PATCH 0/6] PCI Express Advanced Error Reporting Driver
Date: Fri, 11 Mar 2005 23:20:56 -0800	[thread overview]
Message-ID: <20050312072056.GB11236@kroah.com> (raw)
In-Reply-To: <200503120010.j2C0AS4Q020291@snoqualmie.dp.intel.com>

On Fri, Mar 11, 2005 at 04:10:28PM -0800, long wrote:
> 
> -	Report the errors to user.

This is done through the syslog, right?  Is that acceptable?

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.

thanks,

greg k-h

  reply	other threads:[~2005-03-12  8:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

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=20050312072056.GB11236@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=tlnguyen@snoqualmie.dp.intel.com \
    --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 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.