public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Holzheu <holzheu2@linux.vnet.ibm.com>
Cc: johnpol@2ka.mipt.ru, mschwid2@de.ltcfwd.linux.ibm.com,
	heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Using kevent for event logging?
Date: Fri, 16 Feb 2007 10:17:42 -0800	[thread overview]
Message-ID: <20070216101742.b3877aca.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070216155708.589cd47a.holzheu2@linux.vnet.ibm.com>

On Fri, 16 Feb 2007 15:57:08 +0100 Michael Holzheu <holzheu2@linux.vnet.ibm.com> wrote:

> Hallo Evgeniy,
> 
> On s390 we are looking for a good mechanism to notify userspace
> about kernel events. Currently such events are handled with printks
> in most cases. There are automation tools, which want to automatically
> react on kernel events. To get the event information, these tools are
> parsing printks, which is not a really good mechanism for that
> purpose.
> 
> When I read about kevents, I was wondering, if it could be used to solve
> this problem. E.g. it would be possible to put an event number into a
> kevent and provide another interface to get the complete event data.
> 

Wouldn't one simply transport the info across netlink, use kevent (or
select/poll/whatever) for readiness notification?

      parent reply	other threads:[~2007-02-16 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 14:57 Using kevent for event logging? Michael Holzheu
2007-02-16 15:06 ` Evgeniy Polyakov
2007-02-16 17:33   ` Michael Holzheu
2007-02-16 17:59     ` Evgeniy Polyakov
2007-02-16 18:17 ` Andrew Morton [this message]

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=20070216101742.b3877aca.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=holzheu2@linux.vnet.ibm.com \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mschwid2@de.ltcfwd.linux.ibm.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